Re: [PATCH] watchdog: pcwd_pci: mark expected switch fall-through

On Fri, Nov 03, 2017 at 04:04:23PM +0100, Wim Van Sebroeck wrote: > Hi Gustavo, > > > In preparation to enabling -Wimplicit-fallthrough, mark switch cases > > where we are expecting to fall through. > > > > Notice that in this particular case I replaced "Fall" with a proper > > "fall through"

Re: [PATCH] watchdog: pcwd_pci: mark expected switch fall-through

On Fri, Nov 03, 2017 at 09:02:33AM -0700, Joe Perches wrote: > On Fri, 2017-11-03 at 08:54 -0700, Guenter Roeck wrote: > > On Fri, Nov 03, 2017 at 04:04:23PM +0100, Wim Van Sebroeck wrote: > > > Hi Gustavo, > > > > > > > In preparation to enabling -Wimplicit-fallthrough, mark switch cases > > > >

Request to add cpupower git to linux-next

Hi Stephen, Could you please add git://git.kernel.org/pub/scm/linux/kernel/git/shuah/linux.git cpupower to linux-next I will be sending pull requests to Rafael Wysocki for cpupower to be included in linux-pm starting soon for 4.15 release. thanks, -- Shuah -- Shuah Khan Sr. Linux Kernel

[PATCH 1/2] platform/x86: dell-wmi-descriptor: check if memory was allocated

devm_kzalloc will return NULL pointer if no memory was allocated. This should be checked. This problem also existed when the driver was dell-wmi.c. Signed-off-by: Mario Limonciello --- drivers/platform/x86/dell-wmi-descriptor.c | 5 + 1 file changed, 5

[PATCH 0/2] Account for uncorrectable failures in probing

Pali raised some concerns around corner case scenarios that probing may fail on dell-wmi-descriptor causing dell-wmi and dell-smbios-wmi to be stuck in infinite deferred probing loops. This patch series accounts for that corner case. Changes since original submission: - Add as second patch that

[PATCH 2/2] platform/x86: dell-*wmi*: Relay failed initial probe to dependent drivers

dell-wmi and dell-smbios-wmi are dependent upon dell-wmi-descriptor finishing probe successfully to probe themselves. Currently if dell-wmi-descriptor fails probing in a non-recoverable way (such as invalid header) dell-wmi and dell-smbios-wmi will continue to try to redo probing due to deferred

Re: [PATCH v3] lib/dlock-list: Scale dlock_lists_empty()

On 11/03/2017 10:22 AM, Davidlohr Bueso wrote: > Instead of the current O(N) implementation, at the cost > of adding an atomic counter, we can convert the call to > an atomic_read(). The counter only serves for accounting > empty to non-empty transitions, and vice versa; therefore > only modified

[PATCH] misc: mic: scif_nodeqp: use swap macro in scif_node_connect

Make use of the swap macro and remove unnecessary variable tmppayload. This makes the code easier to read and maintain. This code was detected with the help of Coccinelle. Signed-off-by: Gustavo A. R. Silva --- drivers/misc/mic/scif/scif_nodeqp.c | 5 + 1 file

[PATCH v2 0/2] ARM: dts: exynos: Updates for Odroid HDMI audio

These patches are intended for v4.16-rc1 as they depend on the HDMI codec patch which is going to be merged in coming merge window. Sylwester Nawrocki (2): ARM: dts: exynos: Switch to dedicated Odroid-XU3 sound card binding ARM: dts: exynos: Add sound support for Odroid XU4

Re: [PATCH v2 0/2] pinctrl: Allow indicating loss of state across suspend/resume

On 11/03/2017 09:11 AM, Tony Lindgren wrote: > * Charles Keepax [171103 10:38]: >> On Thu, Nov 02, 2017 at 04:15:49PM -0700, Florian Fainelli wrote: >>> Hello Linus, >>> >>> It's me again, so I have been thinking about the problem originally >>> reported in: [PATCH

[PATCH v16 06/13] task_isolation: userspace hard isolation from kernel

The existing nohz_full mode is designed as a "soft" isolation mode that makes tradeoffs to minimize userspace interruptions while still attempting to avoid overheads in the kernel entry/exit path, to provide 100% kernel semantics, etc. However, some applications require a "hard" commitment from

[PATCH v16 05/13] Add try_stop_full_tick() API for NO_HZ_FULL

This API checks to see if the scheduler tick can be stopped, and if so, stops it and returns 0; otherwise it returns an error. This is intended for use with task isolation, where we will want to be able to stop the tick synchronously when returning to userspace. Signed-off-by: Chris Metcalf

[PATCH v16 08/13] arch/x86: enable task isolation functionality

In prepare_exit_to_usermode(), call task_isolation_start() for TIF_TASK_ISOLATION tasks. In syscall_trace_enter_phase1(), add the necessary support for reporting syscalls for task-isolation processes. Add task_isolation_remote() calls for the kernel exception types that do not result in signals,

Re: staging: comedi: usbduxfast: Improve unlocking of a mutex in usbduxfast_ai_insn_read()

> FYI, you are responding to someone who is on my blacklist I am curious if this communication setting will ever be adjusted. > and I never accept patches from. The history shows that our collaboration style changed over time. I got a few update suggestions integrated (also by you) because

Re: [PATCH 4/6] hugetlbfs: implement memfd sealing

On 11/03/2017 10:03 AM, David Herrmann wrote: > Hi > > On Tue, Oct 31, 2017 at 7:40 PM, Marc-André Lureau > wrote: >> Implements memfd sealing, similar to shmem: >> - WRITE: deny fallocate(PUNCH_HOLE). mmap() write is denied in >> memfd_add_seals(). write() doesn't

[PATCH 13/15] arm64: add a workaround for GNU gold with ARM64_MODULE_PLTS

CONFIG_CLANG_LTO depends on GNU gold and due to a known bug, the linker crashes when ARM64_MODULE_PLTS is enabled: https://sourceware.org/bugzilla/show_bug.cgi?id=14592 To work around the problem, this change: 1) Enables ARM64_MODULE_PLTS only when it's needed, i.e. when

[PATCH 14/15] arm64: crypto: disable LTO for aes-ce-cipher.c

CONFIG_CLANG_LTO requires the use of clang's integrated assembler, which doesn't understand the inline assembly in aes-ce-cipher.c. Disable LTO for the file to work around the issue. Signed-off-by: Sami Tolvanen --- arch/arm64/crypto/Makefile | 2 +- 1 file changed, 1

Re: [PATCH v5 2/3] KVM: nVMX: Validate the IA32_BNDCFGS on nested VM-entry

On 11/02/2017 11:40 PM, Wanpeng Li wrote: 2017-11-03 14:31 GMT+08:00 Krish Sadhukhan : On 11/02/2017 05:50 PM, Wanpeng Li wrote: From: Wanpeng Li According to the SDM, if the "load IA32_BNDCFGS" VM-entry controls is 1, the following

[PATCH 1/3] rtc: rx8010: Remove duplicate define

Remove duplicate define for RX8010_YEAR Signed-off-by: Akshay Bhat --- drivers/rtc/rtc-rx8010.c | 1 - 1 file changed, 1 deletion(-) diff --git a/drivers/rtc/rtc-rx8010.c b/drivers/rtc/rtc-rx8010.c index 1ed3403..f948f75 100644 --- a/drivers/rtc/rtc-rx8010.c +++

Re: [PATCH v2 1/2] kprobes: propagate error from arm_kprobe_ftrace()

On Fri, 3 Nov 2017 09:53:37 -0500 Josh Poimboeuf wrote: > > > -static void arm_kprobe_ftrace(struct kprobe *p) > > > +static int arm_kprobe_ftrace(struct kprobe *p) > > > { > > > - int ret; > > > + int ret = 0; > > > > > > ret = ftrace_set_filter_ip(_ftrace_ops, > > >

[PATCH 2/3] rtc: rx8010: Specify correct address for RX8010_RESV31

Define for reserved register 31 had the incorrect address. Specify the correct address. Reported-by: Jens-Peter Oswald Signed-off-by: Akshay Bhat --- drivers/rtc/rtc-rx8010.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git

[PATCH 3/3] rtc: rx8010: Fix for incorrect return value

The err variable is not being reset after a successful read. Explicitly reset err variable to account for all return paths. Reported-by: Jens-Peter Oswald Signed-off-by: Akshay Bhat --- drivers/rtc/rtc-rx8010.c | 2 ++ 1 file changed, 2 insertions(+)

Re: [PATCH v2 0/2] pinctrl: Allow indicating loss of state across suspend/resume

* Florian Fainelli [171103 17:04]: > On 11/03/2017 09:11 AM, Tony Lindgren wrote: > The pinctrl provider is losing its state, hence these two patches. OK > > Anyways, the context lost flag should be managed in the PM core for > > the device, so adding linux-pm and Rafael

Re: [PATCH 07/15] arm64: use -mno-implicit-float instead of -mgeneral-regs-only

I think this bug was fixed upstream in LLVM. Do we still want to take this workaround? On Fri, Nov 3, 2017 at 10:11 AM, Sami Tolvanen wrote: > From: Greg Hackmann > > LLVM bug 30792 causes clang's AArch64 backend to crash compiling >

Re: [PATCH v5 2/3] KVM: nVMX: Validate the IA32_BNDCFGS on nested VM-entry

KVM chooses not to support MPX in the guest unless both of these control bits are supported by the platform. On Fri, Nov 3, 2017 at 10:13 AM, Krish Sadhukhan wrote: > > > On 11/02/2017 11:40 PM, Wanpeng Li wrote: >> >> 2017-11-03 14:31 GMT+08:00 Krish Sadhukhan

Re: [PATCH v16 09/13] arch/arm64: enable task isolation functionality

On 11/3/2017 1:32 PM, Mark Rutland wrote: Hi Chris, On Fri, Nov 03, 2017 at 01:04:48PM -0400, Chris Metcalf wrote: In do_notify_resume(), call task_isolation_start() for TIF_TASK_ISOLATION tasks. Add _TIF_TASK_ISOLATION to _TIF_WORK_MASK, and define a local NOTIFY_RESUME_LOOP_FLAGS to check

Re: [PATCH 2/6] shmem: rename functions that are memfd-related

On 11/03/2017 09:36 AM, Marc-André Lureau wrote: > Hi > > - Original Message - >> On 11/03/2017 09:02 AM, Marc-André Lureau wrote: >>> Hi >>> >>> - Original Message - On 10/31/2017 11:40 AM, Marc-André Lureau wrote: > Those functions are called for memfd files, backed by

Re: [PATCH 00/15] Add support for clang LTO

On Fri, Nov 3, 2017 at 11:09 AM, Mark Rutland wrote: ently compile > What's the minimum set of patches necessary to work with clang (ignoring > LTO)? If you have a build of clang-5, then just patch 7 in this series to work around the last compiler bug. If you build clang

Re: [PATCH 13/15] arm64: fix mrs_s/msr_s macros for clang LTO

On Fri, Nov 3, 2017 at 11:06 AM, Mark Rutland wrote: > On Fri, Nov 03, 2017 at 10:53:08AM -0700, Nick Desaulniers wrote: >> These mrs_s and msr_s macros in particular were preventing us from >> linking arm64 with Clang's integrated assembler, regardless of LTO. >> Those

Re: [PATCH 07/15] arm64: use -mno-implicit-float instead of -mgeneral-regs-only

On Fri, Nov 03, 2017 at 10:11:52AM -0700, Sami Tolvanen wrote: > From: Greg Hackmann > > LLVM bug 30792 causes clang's AArch64 backend to crash compiling > arch/arm64/crypto/aes-ce-cipher.c. Replacing -mgeneral-regs-only with > -mno-implicit-float is the suggested

[PATCH] clk: meson: gxbb: fix wrong clock for SARADC

According to the datasheet, the clock gate bit for SARADC is bit[22] in Meson-GXBB/GXL series. Change-Id: Ic4fa58276d2a9ea273eef0a08541fc213ac5ac89 Signed-off-by: Yixun Lan --- drivers/clk/meson/gxbb.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git

[PATCH 3/4] platform/x86: intel-vbtn: support KEY_ROTATE_DISPLAY

The Rotate Lock button event is emitted on the XPS 12 (BIOS A8, but not on BIOS A2). Signed-off-by: Stefan Brüns --- The changes where tested on an XPS 12 with BIOS version A8 (2015-03-03). An earlier BIOS version (A2, ~2013) did not report the event, at least not

[PATCH 0/4] platform/x86: intel-vbtn: Add support for several more switches/buttons

Currently, intel-vbtn only supports the most relevant buttons, although there are several more events, mostly in use by convertibles. This series adds support for three more events. One of these events is a switch (SW_*) event, which is currently not working when using sparse keymaps. The first

[PATCH 1/4] Input: sparse-keymap - send sync event for KE_SW/KW_VSW

Sync events are sent by sparse_keymap_report_entry for normal KEY_* events, and are generated by several drivers after generating SW_* events, so sparse_keymap_report_entry should do the same. Without the sync, events are accumulated in the kernel. Currently, no driver uses sparse-keymap for

Re: [PATCH 00/15] Add support for clang LTO

On Fri, Nov 03, 2017 at 11:11:45AM -0700, Nick Desaulniers wrote: > On Fri, Nov 3, 2017 at 11:09 AM, Mark Rutland wrote: > ently compile > > What's the minimum set of patches necessary to work with clang (ignoring > > LTO)? > > If you have a build of clang-5, then just

[PATCH] sparc64: Fix page table walk for PUD hugepages

For a PUD hugepage entry, we need to propagate bits [32:22] from virtual address to resolve at 4M granularity. However, the current code was incorrectly propagating bits [29:19]. This bug can cause incorrect data to be returned for pages backed with 16G hugepages. Signed-off-by: Nitin Gupta

Re: [Part2 PATCH v7 18/38] crypto: ccp: Implement SEV_PEK_CSR ioctl command

On Wed, Nov 01, 2017 at 04:16:03PM -0500, Brijesh Singh wrote: > The SEV_PEK_CSR command can be used to generate a PEK certificate > signing request. The command is defined in SEV spec section 5.7. > > Cc: Paolo Bonzini > Cc: "Radim Krčmář" > Cc:

[PATCH] staging: unisys: visorchipset: Use common error handling code in setup_crash_devices_work_queue()

From: Markus Elfring Date: Fri, 3 Nov 2017 20:37:03 +0100 * Add a jump target so that a specific error message is stored only once at the end of this function implementation. * Replace four calls of the function "dev_err" by goto statements. This issue was

Re: [PATCH 4/6] hugetlbfs: implement memfd sealing

Hi On Fri, Nov 3, 2017 at 6:12 PM, Mike Kravetz wrote: > On 11/03/2017 10:03 AM, David Herrmann wrote: >> Hi >> >> On Tue, Oct 31, 2017 at 7:40 PM, Marc-André Lureau >> wrote: >>> Implements memfd sealing, similar to shmem: >>> - WRITE: deny

[PATCH 1/2] cgroup: export list of delegatable control files using sysfs

Delegatable cgroup v2 control files may require special handling (e.g. chowning), and the exact list of such files varies between kernel versions (and likely to be extended in the future). To guarantee correctness of this list and simplify the life of userspace (systemd, first of all), let's

Re: [PATCH] Support resetting WARN_ONCE for all architectures

On Fri, 03 Nov 2017 20:38:03 +1100 Michael Ellerman wrote: > Hi Andi, > > Thanks for making it work with the flag, but ... > > Andi Kleen writes: > > diff --git a/lib/bug.c b/lib/bug.c > > index a6a1137d06db..7cb2d41845f7 100644 > > --- a/lib/bug.c >

[PATCH 2/2] cgroup: export list of cgroups v2 features using sysfs

The active development of cgroups v2 sometimes leads to a creation of interfaces, which are not turned on by default (to provide backward compatibility). It's handy to know from userspace, which cgroup v2 features are supported without calculating it based on the kernel version. So, let's export

[PATCH] uvc: Add D3DFMT_L8 support

Microsoft HoloLense UVC sensor uses D3DFMT instead of FOURCC when exposing formats. This add support for D3DFMT_L8 as exposed from the Acer Windows Mixed Reality Headset. Signed-off-by: Nicolas Dufresne --- drivers/media/usb/uvc/uvc_driver.c | 5 +

Re: [PATCH 00/15] Add support for clang LTO

On Fri, Nov 03, 2017 at 05:51:56PM +, Mark Rutland wrote: > Hi, > > On Fri, Nov 03, 2017 at 10:11:44AM -0700, Sami Tolvanen wrote: > > This series adds build system support for compiling the kernel with clang > > Link Time Optimization (LTO), using GNU gold with the LLVMgold plug-in > > for

Re: [PATCH] mm: use in_atomic() in print_vma_addr()

On 11/3/17 11:02 AM, Andrew Morton wrote: On Fri, 03 Nov 2017 01:44:44 +0800 "Yang Shi" wrote: I may not articulate it in the commit log You should have done so ;) Yes, definitely. I could done it much better. Here's the changelog I ended up with: : From:

Re: [PATCH 00/15] Add support for clang LTO

On Fri, Nov 03, 2017 at 05:51:56PM +, Mark Rutland wrote: > Which tree are you testing with? I've tested that this builds on top of Linus' current tree. > I had to create an aarch64-linux-gnu-clang wrapper, too. I'm not sure if > there's build system help to avoid needing that? This appears

Re: [PATCH 09/15] arm64: keep .altinstructions and .altinstr_replacement

This patch can likely be taken regardless of the rest of the series. It would be good to get additional review from the person who added CONFIG_LD_DEAD_CODE_DATA_ELIMINATION maybe? On Fri, Nov 3, 2017 at 10:11 AM, Sami Tolvanen wrote: > Make sure the linker doesn't

[PATCH 0/3] fix SIGNAL_UNKILLABLE && SIGKILL interaction

On 11/02, Oleg Nesterov wrote: > > I need to write the changelog, and perhaps even split this small patch for > better documentation. OK, it is not clear if I answered Eric's concerns or not, let me send the patches for review anyway. I tried to document every change in signal.c. Oleg.

Re: [PATCH 0/9] Trivial fixup for KVM-based rcutorture test framework

On Sat, Nov 4, 2017 at 2:59 AM, Paul E. McKenney wrote: > On Fri, Nov 03, 2017 at 07:17:19PM +0900, SeongJae Park wrote: >> This patchset contains trivial fixup and enhancements for KVM-based >> rcutorture >> test framework. > > Nice updates! These survived some

Applied "spi: sh-msiof: remove redundant pointer dev" to the spi tree

The patch spi: sh-msiof: remove redundant pointer dev has been applied to the spi tree at https://git.kernel.org/pub/scm/linux/kernel/git/broonie/spi.git All being well this means that it will be integrated into the linux-next tree (usually sometime in the next 24 hours) and sent to

Applied "spi: s3c64xx: remove redundant pointer sci" to the spi tree

The patch spi: s3c64xx: remove redundant pointer sci has been applied to the spi tree at https://git.kernel.org/pub/scm/linux/kernel/git/broonie/spi.git All being well this means that it will be integrated into the linux-next tree (usually sometime in the next 24 hours) and sent to

​​ATTN: My Dear

ATTN: My Dear Good news,The BRITISH HIGH COMMISSION has actually verified and discovered that your payment has been unnecessarily Delayed by corrupt officials of the Company who are Trying to divert your fund of $4,700.000.00 Million into their private accounts. Therefore we have obtained an

Re: [PATCH 07/15] arm64: use -mno-implicit-float instead of -mgeneral-regs-only

On Fri, Nov 3, 2017 at 11:52 AM, Mark Rutland wrote: > On Fri, Nov 03, 2017 at 06:31:56PM +, Mark Rutland wrote: >> On Fri, Nov 03, 2017 at 10:11:52AM -0700, Sami Tolvanen wrote: >> > From: Greg Hackmann >> > >> > LLVM bug 30792 causes clang's

Re: [PATCH 3/3] remove the no longer needed SIGNAL_UNKILLABLE check in complete_signal()

On Fri, Nov 3, 2017 at 11:42 AM, Oleg Nesterov wrote: > complete_signal() checks SIGNAL_UNKILLABLE before it starts to destroy the > thread group, today this is wrong in many ways. > > If nothing else, fatal_signal_pending() should always imply that the whole > thread group

[PATCH] Add Frank Rowand to list of enforcement statement endorsers

From: Frank Rowand Add my name to the list. Signed-off-by: Frank Rowand --- Hi Greg, I noticed that there is a double entry for Ivan Safonov, just below where my name goes. I didn't want to create a merge conflict with this patch, so I'm leaving

[PATCH v10 6/8] arm_pmu: Use of_cpu_node_to_id helper

Use the new generic helper, of_cpu_node_to_id(), to map a a phandle to the logical CPU number while parsing the PMU irq affinity. Cc: Will Deacon Acked-by: Mark Rutland Signed-off-by: Suzuki K Poulose ---

[PATCH v10 7/8] dt-bindings: Document devicetree binding for ARM DSU PMU

This patch documents the devicetree bindings for ARM DSU PMU. Cc: Mark Rutland Cc: Will Deacon Cc: devicet...@vger.kernel.org Cc: frowand.l...@gmail.com Acked-by: Rob Herring Signed-off-by: Suzuki K Poulose

[PATCH v10 8/8] perf: ARM DynamIQ Shared Unit PMU support

Add support for the Cluster PMU part of the ARM DynamIQ Shared Unit (DSU). The DSU integrates one or more cores with an L3 memory system, control logic, and external interfaces to form a multicore cluster. The PMU allows counting the various events related to L3, SCU etc, along with providing a

[PATCH v10 1/8] perf: Export perf_event_update_userpage

Export perf_event_update_userpage() so that PMU driver using them, can be built as modules. Cc: Peter Zilstra Signed-off-by: Suzuki K Poulose --- kernel/events/core.c | 1 + 1 file changed, 1 insertion(+) diff --git a/kernel/events/core.c

[PATCH v10 0/8] perf: Support for ARM DynamIQ Shared Unit

This series adds support for the PMU in ARM DynamIQ Shared Unit (DSU). The DSU integrates one or more cores with an L3 memory system, control logic, and external interfaces to form a multicore cluster. The PMU allows counting the various events related to L3, SCU etc, using 32bit independent

Re: [PATCH 00/15] Add support for clang LTO

Hi, On Fri, Nov 03, 2017 at 10:11:44AM -0700, Sami Tolvanen wrote: > This series adds build system support for compiling the kernel with clang > Link Time Optimization (LTO), using GNU gold with the LLVMgold plug-in > for linking. Some background for clang's LTO support is available here: > >

[PATCH v10 3/8] coresight: of: Use of_cpu_node_to_id helper

Reuse the new generic helper, of_cpu_node_to_id() to map a given CPU phandle to a logical CPU number. Acked-by: Mathieu Poirier Tested-by: Leo Yan Signed-off-by: Suzuki K Poulose --- Changes since V4: - Fix a regression

Re: [PATCH 4/6] hugetlbfs: implement memfd sealing

On 11/03/2017 10:41 AM, David Herrmann wrote: > Hi > > On Fri, Nov 3, 2017 at 6:12 PM, Mike Kravetz wrote: >> On 11/03/2017 10:03 AM, David Herrmann wrote: >>> Hi >>> >>> On Tue, Oct 31, 2017 at 7:40 PM, Marc-André Lureau >>> wrote:

Re: [PATCH] fs/nilfs2: Convert timers to use timer_setup()

2017-10-17 8:59 GMT+09:00 Kees Cook : > In preparation for unconditionally passing the struct timer_list pointer to > all timer callbacks, switch to using the new timer_setup() and from_timer() > to pass the timer pointer explicitly. This requires adding a pointer to > hold

Re: [f2fs-dev] [PATCH 2/2] f2fs: support quota sys files

On 11/03, Chao Yu wrote: > On 2017/11/3 11:37, Jaegeuk Kim wrote: > > On 11/02, Chao Yu wrote: > >> On 2017/10/31 11:40, Jaegeuk Kim wrote: > >>> This patch supports hidden quota files in the system, which will be used > >>> for > >>> Android. It requires up-to-date f2fs-tools later than v1.9.0.

Re: [PATCH] MAINTAINERS: add maintainer for tools/power/cpupower

Hi Shuah, On Thursday, November 02, 2017 01:19:47 PM Shuah Khan wrote: > Based on discussions with Rafael J. Wysocki, cpupower is need of an > active maintainer. I decided to on take the task of maintaining this > tool. Thanks. It is very much appreciated! I had a motorcycle accident and had to

[PATCH 2/3] protect the SIGNAL_UNKILLABLE tasks from !sig_kernel_only() signals

Change sig_task_ignored() to drop the SIG_DFL && !sig_kernel_only() signals even if force == T. This simplifies the next change and this matches the same check in get_signal() which will drop these signals anyway. Signed-off-by: Oleg Nesterov --- kernel/signal.c | 2 +- 1 file

[PATCH 1/3] protect the traced SIGNAL_UNKILLABLE tasks from SIGKILL

The comment in sig_ignored() says "Tracers may want to know about even ignored signals" but SIGKILL can not be reported to debugger and it is just wrong to return 0 in this case: SIGKILL should only kill the SIGNAL_UNKILLABLE task if it comes from the parent ns. Change sig_ignored() to ignore

[PATCH 3/3] remove the no longer needed SIGNAL_UNKILLABLE check in complete_signal()

complete_signal() checks SIGNAL_UNKILLABLE before it starts to destroy the thread group, today this is wrong in many ways. If nothing else, fatal_signal_pending() should always imply that the whole thread group (except ->group_exit_task if it is not NULL) is killed, this check breaks the rule.

[RFC PATCH] scripts: checkpatch.pl: remove obsolete in_atomic rule

checkpatch.pl still reports the below in_atomic warning: WARNING: use of in_atomic() is incorrect outside core kernel code + if (in_atomic()) But, in_atomic() has been used outside kernel dir for a long time, and even drivers. So, remove the obsolete rule even though they can be ignored.

Re: [PATCH] Input: cyttsp4 - Fix error on calculating memory size passed to krealloc.

On Thu, Nov 02, 2017 at 08:49:35PM -0700, Vince Kim wrote: > Hello Dmitry, > > I attached patch with signed-off-by. *sigh* did you try compile that? + if (si->si_ofs.test_ofs <= si->si_ofs.cydata_ofs) + dev_err(cd->dev, "%s: invalid offset test_ofs:%zd, cydata_ofs:%zd \n",

[PATCH] staging/rts5208/rtsx: Improve unlocking of a mutex in rtsx_resume()

From: Markus Elfring Date: Fri, 3 Nov 2017 20:02:22 +0100 * Add a jump target so that a call of the function "mutex_unlock" is stored only twice in this function implementation. * Replace two calls by goto statements. This issue was detected by using the

[PATCH v2] selftests/ftrace: Introduce exit_pass and exit_fail

As same as other results, introduce exit_pass and exit_fail functions so that we can easily understand what will happen. Signed-off-by: Masami Hiramatsu --- Changes in v2: - Restore "this must fail" comment (Thanks Steve!) --- tools/testing/selftests/ftrace/ftracetest

Re: usb/sound/usx2y: WARNING in usb_stream_start

On Fri, 03 Nov 2017 15:44:59 +0100, Andrey Konovalov wrote: > > Hi! > > I've got the following report while fuzzing the kernel with syzkaller. > > On commit 3a99df9a3d14cd866b5516f8cba515a3bfd554ab (4.14-rc7+). > > Looks like there's no check for the actual endpoint types. > > usb 1-1: BOGUS

Re: [PATCH net-next 5/6] net: hns3: add support for nway_reset

On 11/02/2017 09:18 PM, Lipeng wrote: > From: Fuyun Liang > > This patch adds nway_reset support for ethtool cmd. > > Signed-off-by: Fuyun Liang > Signed-off-by: Lipeng > --- >

Re: [PATCH net-next 4/6] net: hns3: add support for set_link_ksettings

On 11/02/2017 09:18 PM, Lipeng wrote: > From: Fuyun Liang > > This patch adds set_link_ksettings support for ethtool cmd. > > Signed-off-by: Fuyun Liang > Signed-off-by: Lipeng > --- >

Re: [PATCH] USB: dummy-hcd: don't set gadget.speed in dummy_hub_control()

On Fri, 3 Nov 2017, Roger Quadros wrote: > There will never be a case when gadget.speed isn't already > USB_SPEED_FULL if connection is not USB-3 and gadget.speed > is not USB_SPEED_HIGH or USB_SPEED_LOW. > > Remove the unnecessary code. > > Signed-off-by: Roger Quadros > --- >

[PATCH v10 2/8] of: Add helper for mapping device node to logical CPU number

Add a helper to map a device node to a logical CPU number to avoid duplication. Currently this is open coded in different places (e.g gic-v3, coresight). The helper tries to map device node to a "possible" logical CPU id, which may not be online yet. It is the responsibility of the user to make

Re: [PATCH 13/15] arm64: fix mrs_s/msr_s macros for clang LTO

These mrs_s and msr_s macros in particular were preventing us from linking arm64 with Clang's integrated assembler, regardless of LTO. Those macros ran into: https://bugs.llvm.org/show_bug.cgi?id=19749. So while I appreciate how clever they are, they prevent us from assembling with Clang so I

Re: [PATCH 0/9] Trivial fixup for KVM-based rcutorture test framework

On Fri, Nov 03, 2017 at 07:17:19PM +0900, SeongJae Park wrote: > This patchset contains trivial fixup and enhancements for KVM-based rcutorture > test framework. Nice updates! These survived some rcutorture testing, so I have queued them for further testing and review. I did update the commit

Re: [PATCH 00/15] Add support for clang LTO

Hi Mark, El Fri, Nov 03, 2017 at 05:51:56PM + Mark Rutland ha dit: > On Fri, Nov 03, 2017 at 10:11:44AM -0700, Sami Tolvanen wrote: > > This series adds build system support for compiling the kernel with clang > > Link Time Optimization (LTO), using GNU gold with the LLVMgold plug-in > > for

Re: [PATCH 13/15] arm64: fix mrs_s/msr_s macros for clang LTO

On Fri, Nov 03, 2017 at 10:53:08AM -0700, Nick Desaulniers wrote: > These mrs_s and msr_s macros in particular were preventing us from > linking arm64 with Clang's integrated assembler, regardless of LTO. > Those macros ran into: https://bugs.llvm.org/show_bug.cgi?id=19749. > So while I appreciate

Re: [PATCH 00/15] Add support for clang LTO

On Fri, Nov 3, 2017 at 10:51 AM, Mark Rutland wrote: > I had to create an aarch64-linux-gnu-clang wrapper, too. I'm not sure if > there's build system help to avoid needing that? Gah! So a BIG difference with Clang vs GCC for cross compiling is that Clang by default ships

Re: [PATCH 07/15] arm64: use -mno-implicit-float instead of -mgeneral-regs-only

On Fri, Nov 3, 2017 at 11:02 AM, Mark Rutland wrote: > Ah, so I guess this is what I was hitting when testing with clang 5.0.0. Exactly. > I was under the impression that this series was jsut enablnig LTO > support, not clang support generally. Clang is supported at least

Re: [PATCH 01/15] kbuild: add ld-name macro and support for GNU gold

+ Kbuild mailing list and maintainers The use of these ternary like operations will need to be expanded if additional compilers come along (less likely), or additional linkers (more likely, we are looking into lld right now) but we can cross that bridge when we get there. Reviewed-by: Nick

Re: [PATCH 00/15] Add support for clang LTO

On Fri, Nov 03, 2017 at 11:07:04AM -0700, Nick Desaulniers wrote: > On Fri, Nov 3, 2017 at 10:51 AM, Mark Rutland wrote: > > I had to create an aarch64-linux-gnu-clang wrapper, too. I'm not sure if > > there's build system help to avoid needing that? > > Gah! So a BIG

Re: [PATCH 00/15] Add support for clang LTO

On Fri, Nov 3, 2017 at 11:29 AM, Mark Rutland wrote: > On Fri, Nov 03, 2017 at 11:07:04AM -0700, Nick Desaulniers wrote: >> On Fri, Nov 3, 2017 at 10:51 AM, Mark Rutland wrote: >> > I had to create an aarch64-linux-gnu-clang wrapper, too. I'm not sure

[PATCH] mm: filemap: remove include of hardirq.h

in_atomic() has been moved to include/linux/preempt.h, and the filemap.c doesn't use in_atomic() directly at all, so it sounds unnecessary to include hardirq.h. With removing hardirq.h, around 32 bytes can be saved for x86_64 bzImage with allnoconfig. Signed-off-by: Yang Shi

[PATCH v1 1/2] x86/mm/kasan: don't use vmemmap_populate() to initialize shadow

The kasan shadow is currently mapped using vmemmap_populate() since that provides a semi-convenient way to map pages into init_top_pgt. However, since that no longer zeroes the mapped pages, it is not suitable for kasan, which requires zeroed shadow memory. Add kasan_populate_shadow() interface

[PATCH v1 2/2] arm64/mm/kasan: don't use vmemmap_populate() to initialize shadow

The kasan shadow is currently mapped using vmemmap_populate() since that provides a semi-convenient way to map pages into init_top_pgt. However, since that no longer zeroes the mapped pages, it is not suitable for kasan, which requires zeroed shadow memory. Add kasan_populate_shadow() interface

[PATCH v1 0/2] don't use vmemmap_populate() to initialize shadow

Andrey Ryabinin asked to replace the three patches in my series: x86-kasan-add-and-use-kasan_map_populate.patch arm64-kasan-add-and-use-kasan_map_populate.patch arm64-kasan-avoid-using-vmemmap_populate-to-initialise-shadow.patch With two patches in this thread: x86/mm/kasan: don't use

[PATCH] x86: kvm: mmu: make kvm_mmu_clear_all_pte_masks static

The kvm_mmu_clear_all_pte_masks interface is only used by kvm_mmu_module_init locally, and does not need to be called by other module, make it static. This patch cleans up sparse warning: symbol 'kvm_mmu_clear_all_pte_masks' was not declared. Should it be static? Signed-off-by: Gimcuan Hui

Re: [PATCH 07/15] arm64: use -mno-implicit-float instead of -mgeneral-regs-only

On Fri, Nov 03, 2017 at 06:31:56PM +, Mark Rutland wrote: > On Fri, Nov 03, 2017 at 10:11:52AM -0700, Sami Tolvanen wrote: > > From: Greg Hackmann > > > > LLVM bug 30792 causes clang's AArch64 backend to crash compiling > > arch/arm64/crypto/aes-ce-cipher.c. Replacing

Re: T20 Cpuidle Freeze

On 03.11.2017 16:07, Marcel Ziswiler wrote: > Hi Rafael, dear community > > One of our customers reported seeing freezes when running the LTS Linux > kernel 4.9.x on our Toradex Colibri T20 modules [1]. I was able to > reproduce a complete SoC lock-up after a few minutes also running the > latest

Re: [PATCH 0/3] objtool: sync warning fix and cleanups

On Fri, Nov 03, 2017 at 09:31:42AM -0500, Josh Poimboeuf wrote: > Patch 1 fixes the "x86 instruction decoder differs from kernel" warning. > > Patches 2-3 improve the sync checking so that future warnings will be > more useful. Hm, patch 2 seems to be causing a 0-day bot error which I need to

Re: [PATCH] MAINTAINERS: add maintainer for tools/power/cpupower

On 11/03/2017 12:42 PM, Thomas Renninger wrote: > Hi Shuah, > > > On Thursday, November 02, 2017 01:19:47 PM Shuah Khan wrote: >> Based on discussions with Rafael J. Wysocki, cpupower is need of an >> active maintainer. I decided to on take the task of maintaining this >> tool. > > Thanks. It

Re: [PATCH] selftests/ftrace: Introduce exit_pass and exit_fail

On Wed, 1 Nov 2017 15:18:41 -0600 Shuah Khan wrote: > On 10/31/2017 10:23 PM, Masami Hiramatsu wrote: > > On Tue, 31 Oct 2017 17:44:32 -0400 > > Steven Rostedt wrote: > > > >> On Tue, 31 Oct 2017 23:51:42 +0900 > >> Masami Hiramatsu

[PATCH V0 2/3] perf/x86/intel/bm.c: Add Intel Branch Monitoring support

Currently, the cannonlake family of Intel processors support the branch monitoring feature. Intel's Branch monitoring feature is trying to utilize heuristics to detect the occurrence of an ROP (Return Oriented Programming) attack. A perf-based kernel driver has been used to monitor the occurrence

[PATCH V0 1/3] x86/cpu/intel: Add Cannonlake to Intel family

Add CPUID of Cannonlake (CNL) processors to Intel family list. Signed-off-by: Megha Dey --- arch/x86/include/asm/intel-family.h | 2 ++ 1 file changed, 2 insertions(+) diff --git a/arch/x86/include/asm/intel-family.h b/arch/x86/include/asm/intel-family.h index

[PATCH V0 0/3] perf/x86/intel: Add Branch Monitoring support

This patchset adds support for Intel's branch monitoring feature. This feature uses heuristics to detect the occurrence of an ROP(Return Oriented Programming) or ROP like(JOP: Jump oriented programming) attack. These heuristics are based off certain performance monitoring statistics, measured

<    1   2   3   4   5   6   7   8   9   10   >