Re: [PATCH] IB/core: Make ib_mad_client_id atomic

On Thu, Apr 19, 2018 at 11:55:55PM -0400, Doug Ledford wrote: > On Wed, 2018-04-18 at 16:24 +0200, Håkon Bugge wrote: > > Two kernel threads may get the same value for agent.hi_tid, if the > > agents are registered for different ports. As of now, this works, as > > the agent list is per port. > >

[PATCH 3/2] rtmutex: Use waiter debug init,free magic numbers

... we already use these for regular mutexes, rtmutex can also use it, and while at it rename the whole thing since this is specific to waiters. Signed-off-by: Davidlohr Bueso --- include/linux/poison.h | 4 ++-- kernel/locking/mutex-debug.c | 4 ++--

Re: [PATCH v4 0/3] lan78xx: Read configuration from Device Tree

From: Phil Elwell Date: Thu, 19 Apr 2018 17:59:37 +0100 > The Microchip LAN78XX family of devices are Ethernet controllers with > a USB interface. Despite being discoverable devices it can be useful to > be able to configure them from Device Tree, particularly in low-cost >

Re: [PATCH 04/24] VFS: Add LSM hooks for filesystem context [ver #7]

Paul Moore wrote: > Adding the SELinux mailing list to the CC line; in the future please > include the SELinux mailing list on patches like this. It would also > be very helpful to include "selinux" somewhere in the subject line > when the patch is predominately SELinux

Re: Potential problem with 31e77c93e432dec7 ("sched/fair: Update blocked load when newly idle")

Hi Heiner and Niklas, Le Saturday 14 Apr 2018 à 13:24:20 (+0200), Vincent Guittot a écrit : > Hi Niklas, > > On 13 April 2018 at 00:39, Niklas Söderlund > wrote: > > Hi Vincent, > > > > Thanks for helping trying to figure this out. > > > > On 2018-04-12 15:30:31

Re: [PATCH 2/2] x86/microcode: Do not exit early from __reload_late()

On Fri, Apr 20, 2018 at 12:37:08PM +0200, Borislav Petkov wrote: > Vitezslav reported a case where the > > "Timeout during microcode update!" > > panic would hit. After a deeper look, it turned out that his .config had > CONFIG_HOTPLUG_CPU disabled which practically made save_mc_for_early() a

Re: [virtio-dev] [pci PATCH v7 2/5] virtio_pci: Add support for unmanaged SR-IOV on virtio_pci devices

On Fri, Apr 20, 2018 at 8:28 AM, Michael S. Tsirkin wrote: > On Fri, Apr 20, 2018 at 07:56:14AM -0700, Alexander Duyck wrote: >> > I think for virtio it should include the feature bit, yes. >> > Adding feature bit is very easy - post a patch to the virtio TC mailing >> > list,

Re: [REVIEW][PATCH 22/22] signal/xtensa: Use force_sig_fault where appropriate

On Fri, Apr 20, 2018 at 7:38 AM, Eric W. Biederman wrote: > Filling in struct siginfo before calling force_sig_info a tedious and > error prone process, where once in a great while the wrong fields > are filled out, and siginfo has been inconsistently cleared. > > Simplify

Re: [PATCH] sched/fair: Change sched_feat(x) in !CONFIG_SCHED_DEBUG case

On 20.04.2018 09:57, Peter Zijlstra wrote: > On Mon, Apr 16, 2018 at 10:54:26AM +0200, Philipp Klocke wrote: > >> This patch is motivated by the clang warning Wconstant-logical-operand, >> issued when logically comparing a variable to a constant integer that is >> neither 1 nor 0. It happens for

Re: [RFC PATCH v2 4/6] sched/fair: Introduce an energy estimation helper function

On Fri, Apr 20, 2018 at 03:42:45PM +0100, Quentin Perret wrote: > Hi Leo, > > On Wednesday 18 Apr 2018 at 20:15:47 (+0800), Leo Yan wrote: > > Sorry I introduce mess at here to spread my questions in several > > replying, later will try to ask questions in one replying. Below are > > more

Re: [PATCH 2/2] rtmutex: Reduce top-waiter blocking on a lock

On Fri, 2018-04-20 at 17:50 +0200, Peter Zijlstra wrote: > On Tue, Apr 10, 2018 at 09:27:50AM -0700, Davidlohr Bueso wrote: > > By applying well known spin-on-lock-owner techniques, we can avoid the > > blocking overhead during the process of when the task is trying to take > > the rtmutex. The

Re: [PATCH 0/8] arm: renesas: Change platform dependency to ARCH_RENESAS

On Fri, Apr 20, 2018 at 03:28:26PM +0200, Geert Uytterhoeven wrote: > The first 6 patches can be applied independently by subsystem > maintainers. > The last two patches depend on the first 6 patches, and are thus marked > RFC. Would it not make sense to try to apply everything en masse rather

Re: [RFC PATCH] dt-bindings: add a jsonschema binding example

On Wed, Apr 18, 2018 at 05:29:05PM -0500, Rob Herring wrote: > The current DT binding documentation format of freeform text is painful > to write, review, validate and maintain. > > This is just an example of what a binding in the schema format looks > like. It's using jsonschema vocabulary in a

[PATCH] Input: atmel_mxt_ts - fix reset-gpio for level based irqs

The current reset-gpio support triggers an interrupt storm on platforms using the maxtouch with level based interrupt. The Motorola Droid 4, which I used for some of the tests is not affected, since it uses a level based interrupt. This change avoids the interrupt storm by enabling the device

Re: [PATCH v3 2/2] tracing: remove igrab() iput() call from uprobes.c

On Fri, 20 Apr 2018 09:56:25 -0700 Song Liu wrote: > Caller of uprobe_register is required to keep the inode and containing > mount point referenced. I would add a little more background to why this is the case. Also a possible link to the conversation? Link:

Re: [PATCH v2] x86/cpufeature: guard asm_volatile_goto usage with NO_BPF_WORKAROUND

On 4/20/18 1:19 AM, Peter Zijlstra wrote: On Sat, Apr 14, 2018 at 09:27:38PM -0700, Yonghong Song wrote: This patch adds a preprocessor guard NO_BPF_WORKAROUND around the asm_volatile_goto based static_cpu_has(). NO_BPF_WORKAROUND is set at toplevel Makefile when compiler supports asm-goto.

[PATCH 1/1] media: nec-decoder: remove trailer_space state

From: Daniel Fu Remove STATE_TRAILER_SPACE from state machine. Causing 2 issue: - can not decode the keycode, if it didn't following with another keycode/repeat code - will generate one more code in current logic. i.e. key_right + repeat code + key_left + repeat code.

Re: [PATCH 3/3] lightnvm: pblk: fix smeta write error path

> On 19 Apr 2018, at 09.39, Hans Holmberg > wrote: > > From: Hans Holmberg > > Smeta write errors were previously ignored. Skip these > lines instead and throw them back on the free > list, so the chunks will go through a reset cycle

Re: [PATCH v4 1/2] Documentation: Documentation for qcom, llcc

On 2018-04-18 11:11, Channa wrote: On 2018-04-18 07:52, Rob Herring wrote: On Tue, Apr 17, 2018 at 5:12 PM, wrote: On 2018-04-17 10:43, risha...@codeaurora.org wrote: On 2018-04-16 07:59, Rob Herring wrote: On Tue, Apr 10, 2018 at 01:08:12PM -0700, Rishabh

Re: [regression v4.17-rc0] Re: FORTIFY_SOURCE breaks ARM compilation in -next -- was Re: ARM compile failure in Re: linux-next: Tree for Apr 4

Hi! > >> Hi! Sorry I lost this email in my inbox. It seems this is specific to > >> a particular subset of arm architectures? (My local builds of arm all > >> succeed, for example. Can you send your failing config?) I'll take a > >> closer look on Monday if Daniel doesn't beat me to it. > > > >

[PATCH net-next 1/4] mm: provide a mmap_hook infrastructure

When adding tcp mmap() implementation, I forgot that socket lock had to be taken before current->mm->mmap_sem. syzbot eventually caught the bug. This patch provides a new mmap_hook() method in struct file_operations that might be provided by fs to implement a finer control of whats to be done

[PATCH net-next 0/4] mm,tcp: provide mmap_hook to solve lockdep issue

This patch series provide a new mmap_hook to fs willing to grab a mutex before mm->mmap_sem is taken, to ensure lockdep sanity. This hook allows us to shorten tcp_mmap() execution time (while mmap_sem is held), and improve multi-threading scalability. Eric Dumazet (4): mm: provide a mmap_hook

[PATCH net-next 3/4] tcp: provide tcp_mmap_hook()

Many socket operations can copy data between user and kernel space while socket lock is held. This means mm->mmap_sem can be taken after socket lock. When implementing tcp mmap(), I forgot this and syzbot was kind enough to point this to my attention. This patch adds tcp_mmap_hook(), allowing us

Re: [RFC PATCH ghak32 V2 10/13] audit: add containerid support for seccomp and anom_abend records

On Thu, Apr 19, 2018 at 8:42 PM, Richard Guy Briggs wrote: > On 2018-04-18 21:31, Paul Moore wrote: >> On Fri, Mar 16, 2018 at 5:00 AM, Richard Guy Briggs wrote: >> > Add container ID auxiliary records to secure computing and abnormal end >> > standalone

Re: [RFC PATCH ghak32 V2 06/13] audit: add support for non-syscall auxiliary records

On Thu, Apr 19, 2018 at 9:23 PM, Richard Guy Briggs wrote: > On 2018-04-18 20:39, Paul Moore wrote: >> On Fri, Mar 16, 2018 at 5:00 AM, Richard Guy Briggs wrote: >> > Standalone audit records have the timestamp and serial number generated >> > on the fly and as

Re: [kcov] watchdog: BUG: soft lockup - CPU#0 stuck for 22s! [swapper/0:1]

On Fri, Apr 20, 2018 at 05:08:23PM +0300, Andrey Ryabinin wrote: > > > On 04/19/2018 06:01 AM, Fengguang Wu wrote: > > Hello, > > > > FYI this happens in mainline kernel 4.17.0-rc1. > > It at least dates back to v4.8 . > > > > [ 25.697463] > > [ 25.697463] Start testing find_bit() with

Re: [RESEND][PATCH 2/4] NFC: st21nfca: Fix memory OOB and leak issues in connectivity events handler

On Fri, Apr 20, 2018 at 03:39:46PM +0300, Andy Shevchenko wrote: > On Wed, 2018-04-18 at 15:35 +0530, Amit Pundir wrote: > > > if (skb->data[transaction->aid_len + 2] != > > - NFC_EVT_TRANSACTION_PARAMS_TAG) > > + NFC_EVT_TRANSACTION_PARAMS_TAG || > > +

Applied "regulator: tps6586x: Add support for TPS658624" to the regulator tree

The patch regulator: tps6586x: Add support for TPS658624 has been applied to the regulator tree at https://git.kernel.org/pub/scm/linux/kernel/git/broonie/regulator.git All being well this means that it will be integrated into the linux-next tree (usually sometime in the next 24 hours)

Re: linux-next: Tree for Apr 20 (media/platform/marvell-ccic/)

On 04/19/18 23:11, Stephen Rothwell wrote: > Hi all, > > Changes since 20180419: > > I have added a patch to the arm-current tree to fix build problems > discovered overnight. > > Non-merge commits (relative to Linus' tree): 1278 > 1324 files changed, 47025 insertions(+), 20625 deletions(-) >

Applied "regulator: Don't return or expect -errno from of_map_mode()" to the regulator tree

The patch regulator: Don't return or expect -errno from of_map_mode() has been applied to the regulator tree at https://git.kernel.org/pub/scm/linux/kernel/git/broonie/regulator.git All being well this means that it will be integrated into the linux-next tree (usually sometime in the

Applied "spi: simplify getting .drvdata" to the spi tree

The patch spi: simplify getting .drvdata 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 Linus during the

RE: [PATCH] platform/x86: Kconfig: Fix dell-laptop dependency chain.

> -Original Message- > From: platform-driver-x86-ow...@vger.kernel.org [mailto:platform-driver-x86- > ow...@vger.kernel.org] On Behalf Of Randy Dunlap > Sent: Friday, April 20, 2018 12:53 PM > To: Limonciello, Mario; dvh...@infradead.org; Andy Shevchenko > Cc: LKML;

Re: general protection fault in kernfs_kill_sb

On Fri, Apr 20, 2018 at 09:31:58AM +0200, Michal Hocko wrote: > On Fri 20-04-18 14:29:39, Tetsuo Handa wrote: > > Eric Biggers wrote: > > > But, there is still a related bug: when mounting sysfs, if > > > register_shrinker() > > > fails in sget_userns(), then kernfs_kill_sb() gets called, which

Re: [RESEND PATCH 1/1] drm/i915/glk: Add MODULE_FIRMWARE for Geminilake

On Tue, Apr 17, 2018 at 12:02:52PM +0300, Jani Nikula wrote: > On Mon, 16 Apr 2018, "Srivatsa, Anusha" wrote: > >>-Original Message- > >>From: Jani Nikula [mailto:jani.nik...@linux.intel.com] > >>Sent: Wednesday, April 11, 2018 5:27 AM > >>To: Ian W MORRISON

PROBLEM: error due to conflicting types during build of kselftests

hello, the following is the error found... --- protection_keys.c:421:5: error: conflicting types for ‘pkey_set’ int pkey_set(int pkey, unsigned long rights, unsigned long flags) ^~~~

Re: [PATCH] x86/MCE, EDAC/mce_amd: Save all aux registers on SMCA systems

On Fri, Apr 20, 2018 at 01:05:17PM +, Ghannam, Yazen wrote: > Okay, I can do that. What about using mce_rdmsrl()? The value gets set to > 0 and a user gets a single warning. This may be more clear to the user. Also, > it shouldn't affect code that checks for non-zero values, like in >

Re: [PATCH v4 05/22] iommu: introduce iommu invalidate API function

Hi Jacob, On Mon, Apr 16, 2018 at 10:48:54PM +0100, Jacob Pan wrote: [...] > +/** > + * enum iommu_inv_granularity - Generic invalidation granularity > + * > + * When an invalidation request is sent to IOMMU to flush translation caches, > + * it may carry different granularity. These granularity

[PATCH v2] clk: add duty cycle support

Add the possibility to apply and query the clock signal duty cycle ratio. This is useful when the duty cycle of the clock signal depends on some other parameters controlled by the clock framework. For example, the duty cycle of a divider may depends on the raw divider setting (ratio = N / div) ,

Re: Clang arm64 build is broken

Hi Andrey, On Fri, Apr 20, 2018 at 04:59:35PM +0200, Andrey Konovalov wrote: > On Fri, Apr 20, 2018 at 10:13 AM, Marc Zyngier wrote: > >> The issue is that > >> clang doesn't know about the "S" asm constraint. I reported this to > >> clang [2], and hopefully this will get

Re: [PATCH 2/2] rtmutex: Reduce top-waiter blocking on a lock

On Tue, Apr 10, 2018 at 09:27:50AM -0700, Davidlohr Bueso wrote: > By applying well known spin-on-lock-owner techniques, we can avoid the > blocking overhead during the process of when the task is trying to take > the rtmutex. The idea is that as long as the owner is running, there is a > fair

Re: [Patch v2] Storvsc: Select channel based on available percentage of ring buffer to write

On Thu, 19 Apr 2018 14:54:24 -0700 Long Li wrote: > From: Long Li > > This is a best effort for estimating on how busy the ring buffer is for > that channel, based on available buffer to write in percentage. It is still > possible that at the

[PATCH 2/5] ARM: dts: stih407-pinctrl: Fix complain about IRQ_TYPE_NONE usage

From: Patrice Chotard Since commit 83a86fbb5b56 ("irqchip/gic: Loudly complain about the use of IRQ_TYPE_NONE") kernel is complaining about the IRQ_TYPE_NONE usage which shouldn't be used. Use IRQ_TYPE_LEVEL_HIGH instead. Signed-off-by: Patrice Chotard

[PATCH 0/5] ARM: dts: STi: Fix complain about IRQ_TYPE_NONE_usage

From: Patrice Chotard Fix the STi following DT files which make usage of IRQ_TYPE_NONE flag: _ stih407-family.dtsi _ stih407-pinctrl.dtsi _ stih407.dtsi _ stih410.dtsi _ stihxxx-b2120.dtsi Patrice Chotard (5): ARM: dts: stih407-family: Fix complain about

[git pull] vfs fixes

Assorted fixes. Some of that is only a matter with fault injection (broken handling of small allocation failure in various mount-related places), but the last one is a root-triggerable stack overflow, and combined with userns it gets really nasty ;-/ The following changes since commit

[PATCH 5/5] ARM: dts: stihxxx-b2120: Fix complain about IRQ_TYPE_NONE usage

From: Patrice Chotard Since commit 83a86fbb5b56 ("irqchip/gic: Loudly complain about the use of IRQ_TYPE_NONE") kernel is complaining about the IRQ_TYPE_NONE usage which shouldn't be used. Use IRQ_TYPE_LEVEL_HIGH instead. Signed-off-by: Patrice Chotard

[PATCH 1/5] ARM: dts: stih407-family: Fix complain about IRQ_TYPE_NONE usage

From: Patrice Chotard Since commit 83a86fbb5b56 ("irqchip/gic: Loudly complain about the use of IRQ_TYPE_NONE") kernel is complaining about the IRQ_TYPE_NONE usage which shouldn't be used. Use IRQ_TYPE_LEVEL_HIGH instead. Signed-off-by: Patrice Chotard

Re: [PATCH ghak80 V1] audit: add syscall information to FEATURE_CHANGE records

On Fri, Apr 20, 2018 at 9:46 AM, Richard Guy Briggs wrote: > On 2018-04-17 18:06, Paul Moore wrote: >> On Wed, Apr 11, 2018 at 8:46 AM, Richard Guy Briggs wrote: >> > Tie syscall information to FEATURE_CHANGE calls since it is a result of >> > user action. >> >

[PATCH 4/5] ARM: dts: stih410: Fix complain about IRQ_TYPE_NONE usage

From: Patrice Chotard Since commit 83a86fbb5b56 ("irqchip/gic: Loudly complain about the use of IRQ_TYPE_NONE") kernel is complaining about the IRQ_TYPE_NONE usage which shouldn't be used. Use IRQ_TYPE_LEVEL_HIGH instead. Signed-off-by: Patrice Chotard

[pci PATCH v8 0/4] Add support for unmanaged SR-IOV

This series is meant to add support for SR-IOV on devices when the VFs are not managed by the kernel. Examples of recent patches attempting to do this include: virto - https://patchwork.kernel.org/patch/10241225/ pci-stub - https://patchwork.kernel.org/patch/10109935/ vfio -

[pci PATCH v8 1/4] pci: Add pci_sriov_configure_simple for PFs that don't manage VF resources

This patch adds a common configuration function called pci_sriov_configure_simple that will allow for managing VFs on devices where the PF is not capable of managing VF resources. Signed-off-by: Alexander Duyck Tested-by: Mark Rustad ---

Re: Clang arm64 build is broken

On 20/04/18 17:30, Nick Desaulniers wrote: > On Fri, Apr 20, 2018 at 1:13 AM Marc Zyngier wrote: >> Clang isn't >> really supported to build the arm64 kernel anyway > > Can you expand on this? There are millions of arm64 devices shipping with > Clang built Linux kernels.

Re: [PATCH] crypto: testmgr: Allow different compression results

On Wed, Apr 11, 2018 at 08:28:32PM +0200, Jan Glauber wrote: > From: Mahipal Challa > > The following error is triggered by the ThunderX ZIP driver > if the testmanager is enabled: > > [ 199.069437] ThunderX-ZIP :03:00.0: Found ZIP device 0 177d:a01a on > Node 0 > [

[PATCH v3 1/2] tracing: fix bad use of igrab in trace_uprobe.c

As Miklos reported and suggested: This pattern repeats two times in trace_uprobe.c and in kernel/events/core.c as well: ret = kern_path(filename, LOOKUP_FOLLOW, ); if (ret) goto fail_address_parse; inode = igrab(d_inode(path.dentry)); path_put(); And

Re: [PATCH 2/2] ubi: introduce ubi.nocheck parameter to skip CRC check when attaching ubi vol

On Fri, 20 Apr 2018 10:52:41 +0200 Quentin Schulz wrote: > There's already ECC on NAND pages so there may be no need for one to > check the CRC of a UBI volume. That's true that ECC can help detecting corruptions, but I don't think this is the actual reason for

[PATCH] lib: avoid soft lockup in test_find_first_bit()

test_find_first_bit() is intentionally sub-optimal, and may cause soft lockup due to long time of run on some systems. So decrease length of bitmap to traverse to avoid lockup. With the change below, time of test execution doesn't exceed 0.2 seconds on my testing system. Signed-off-by: Yury

[PATCH v2 0/2] sparc64: Add privileged ADI driver

ADI is a feature supported on SPARC M7 and newer processors to allow hardware to catch rogue accesses to memory. ADI is supported for data fetches only and not instruction fetches. An app can enable ADI on its data pages, set version tags on them and use versioned addresses to access the data

Re: [PATCH V3] USB: Increment wakeup count on remote wakeup.

On Fri, 20 Apr 2018, Ravi Chandra Sadineni wrote: > On chromebooks we depend on wakeup count to identify the wakeup source. > But currently USB devices do not increment the wakeup count when they > trigger the remote wake. This patch addresses the same. > > Resume condition is reported

Re: [RFC] mm: kmemleak: replace __GFP_NOFAIL to GFP_NOWAIT in gfp_kmemleak_mask

On Fri, Apr 20, 2018 at 7:50 PM, Catalin Marinas wrote: > On Sat, Apr 21, 2018 at 12:58:33AM +0800, Chunyu Hu wrote: >> __GFP_NORETRY and __GFP_NOFAIL are combined in gfp_kmemleak_mask now. >> But it's a wrong combination. As __GFP_NOFAIL is blockable, but >>

Re: [PATCH] platform/x86: Kconfig: Fix dell-laptop dependency chain.

On 04/20/18 10:42, Mario Limonciello wrote: > As reported by Randy Dunlap: >>> WARNING: unmet direct dependencies detected for DELL_SMBIOS >>> Depends on [m]: X86 [=y] && X86_PLATFORM_DEVICES [=y] >>> && (DCDBAS [=m] || >>> DCDBAS [=m]=n) && (ACPI_WMI [=n] || ACPI_WMI [=n]=n) >>> Selected

Re: [PATCH ghak80 V1] audit: add syscall information to FEATURE_CHANGE records

On 2018-04-20 11:58, Paul Moore wrote: > On Fri, Apr 20, 2018 at 9:46 AM, Richard Guy Briggs wrote: > > On 2018-04-17 18:06, Paul Moore wrote: > >> On Wed, Apr 11, 2018 at 8:46 AM, Richard Guy Briggs > >> wrote: > >> > Tie syscall information to FEATURE_CHANGE

[PATCH V4] USB: Increment wakeup count on remote wakeup.

On chromebooks we depend on wakeup count to identify the wakeup source. But currently USB devices do not increment the wakeup count when they trigger the remote wake. This patch addresses the same. Resume condition is reported differently on USB 2.0 and USB 3.0 devices. On USB 2.0 devices, a

[PATCH V5] USB: Increment wakeup count on remote wakeup.

On chromebooks we depend on wakeup count to identify the wakeup source. But currently USB devices do not increment the wakeup count when they trigger the remote wake. This patch addresses the same. Resume condition is reported differently on USB 2.0 and USB 3.0 devices. On USB 2.0 devices, a

[PATCH v4] tracing: remove igrab() iput() call from uprobes.c

Caller of uprobe_register is required to keep the inode and containing mount point referenced. There was misuse of igrab() in uprobes.c and trace_uprobe.c. This is because igrab() will not prevent umount of the containing mount point. To fix this, we added path to struct trace_uprobe, which keeps

Re: [PATCH V3] USB: Increment wakeup count on remote wakeup.

On Fri, Apr 20, 2018 at 10:29 AM, Alan Stern wrote: > On Fri, 20 Apr 2018, Ravi Chandra Sadineni wrote: > >> On chromebooks we depend on wakeup count to identify the wakeup source. >> But currently USB devices do not increment the wakeup count when they >> trigger the

Re: [PATCH] parisc: time: Convert read_persistent_clock() to read_persistent_clock64()

On 20.04.2018 17:23, Arnd Bergmann wrote: > On Thu, Apr 19, 2018 at 8:51 AM, Baolin Wang wrote: >> The read_persistent_clock() uses a timespec, which is not year 2038 safe >> on 32bit systems. On parisc architecture, we have implemented generic RTC >> drivers that can be

Re: [PATCH v4] tracing: remove igrab() iput() call from uprobes.c

On Fri, 20 Apr 2018 18:36:38 + Song Liu wrote: > > On Apr 20, 2018, at 11:29 AM, Steven Rostedt wrote: > > > > On Fri, 20 Apr 2018 11:08:47 -0700 > > Song Liu wrote: > > > >> For uprobes.c sisde, igrab() is not

RE: [Patch v4] cifs: Allocate validate negotiation request through kmalloc

> Subject: Re: [Patch v4] cifs: Allocate validate negotiation request through > kmalloc > > Looks good, but I have two possibly style-related comments. > > On 4/19/2018 5:38 PM, Long Li wrote: > > From: Long Li > > > > The data buffer allocated on the stack can't be

[PATCH 0/1] Add two IR keymaps for NVIDIA devices

Adds two IR keymaps for NVIDIA devices. The RC types are SONY12 and NEC. Jun Yan (1): media: rc: Add NVIDIA IR keymapping drivers/media/rc/keymaps/Makefile| 2 + drivers/media/rc/keymaps/rc-nvidia-nec.c | 66 drivers/media/rc/keymaps/rc-nvidia.c | 66

[PATCH 1/1] media: rc: Add NVIDIA IR keymapping

From: Jun Yan Add keymap with NEC and SONY12 protocol for NVIDIA IR Signed-off-by: Jun Yan Signed-off-by: marting Signed-off-by: Daniel Fu Signed-off-by: Vladislav Zhurba ---

Re: [PATCH ghak80 V1] audit: add syscall information to FEATURE_CHANGE records

On Fri, Apr 20, 2018 at 1:48 PM, Richard Guy Briggs wrote: > On 2018-04-20 11:58, Paul Moore wrote: >> On Fri, Apr 20, 2018 at 9:46 AM, Richard Guy Briggs wrote: >> > On 2018-04-17 18:06, Paul Moore wrote: >> >> On Wed, Apr 11, 2018 at 8:46 AM, Richard Guy

RE: [Patch v4] cifs: Allocate validate negotiation request through kmalloc

> Subject: Re: [Patch v4] cifs: Allocate validate negotiation request through > kmalloc > > On 4/20/2018 2:41 PM, Long Li wrote: > >> Subject: Re: [Patch v4] cifs: Allocate validate negotiation request > >> through kmalloc > >> > >> Looks good, but I have two possibly style-related comments. > >>

[PATCH 3/4] sh: remove unused rtc_sh_get/set_time infrastructure

All platforms are now converted to RTC drivers, so this has become obsolete. The board_time_init() callback still has one caller, but could otherwise also get killed. This removes one more usage of the deprecated timespec structure, which overflows in y2038. Signed-off-by: Arnd Bergmann

Re: [PATCH V1 4/4] qcom: spmi-wled: Add auto-calibration logic support

On Thu 19 Apr 22:43 PDT 2018, kgu...@codeaurora.org wrote: > On 2018-04-19 21:28, Bjorn Andersson wrote: > > On Thu 19 Apr 03:45 PDT 2018, kgu...@codeaurora.org wrote: > > > On 2017-12-05 11:10, Bjorn Andersson wrote: [..] > > > > When is this feature needed? > > > > > > > This feature is needed

[PATCH] [RESEND 2] scsi: esas2r: use ktime_get_real_seconds()

do_gettimeofday() is deprecated because of the y2038 overflow. Here, we use the result to pass into a 32-bit field in the firmware, which still risks an overflow, but if the firmware is written to expect unsigned values, it can at least last until y2106, and there is not much we can do about it.

Re: [RFC PATCH ghak32 V2 05/13] audit: add containerid support for ptrace and signals

On Thu, Apr 19, 2018 at 9:03 PM, Richard Guy Briggs wrote: > On 2018-04-18 20:32, Paul Moore wrote: >> On Fri, Mar 16, 2018 at 5:00 AM, Richard Guy Briggs wrote: ... >> > /* >> > * audit_log_container_info - report container info >> > - * @tsk: task to be

Re: [PATCH net-next 2/2] netns: isolate seqnums to use per-netns locks

On Fri, Apr 20, 2018 at 03:56:28PM +0200, Christian Brauner wrote: > On Wed, Apr 18, 2018 at 11:52:47PM +0200, Christian Brauner wrote: > > On Wed, Apr 18, 2018 at 11:55:52AM -0500, Eric W. Biederman wrote: > > > Christian Brauner writes: > > > > > > > Now that it's

[PATCH] MAINTAINERS: Update e-mail address for Andrea Parri

I moved to Amarula Solutions; switch to work e-mail address. Signed-off-by: Andrea Parri Cc: Alan Stern Cc: Will Deacon Cc: Peter Zijlstra Cc: Boqun Feng Cc:

Re: Clang arm64 build is broken

On Fri, Apr 20, 2018 at 9:36 AM Marc Zyngier wrote: > On 20/04/18 17:30, Nick Desaulniers wrote: > > On Fri, Apr 20, 2018 at 1:13 AM Marc Zyngier wrote: > >> Clang isn't > >> really supported to build the arm64 kernel anyway > > > > Can you expand on

Re: [RFC] perf/core: what is exclude_idle supposed to do

On Fri, 20 Apr 2018, Vince Weaver wrote: > > AFAICT it works on Power and possibly ARM. > > at least some ARMs are a bit more honest about it than x86 > > ivybridge: > Performance counter stats for '/bin/ls': > 1,368,162 instructions > 1,368,162 instructions:I > >

Re: [PATCH] sched/fair: Change sched_feat(x) in !CONFIG_SCHED_DEBUG case

On Fri, Apr 20, 2018 at 06:29:07PM +0200, Philipp Klocke wrote: > The gain is stopping a warning that clutters the output log of clang. Well, you should not be using clang anyway. It is known to miscompile the kernel. > To improve readability, one can drop the ifdef-structure and just keep > the

Re: [RESEND PATCH] crypto: Add zstd support

On Fri, Mar 30, 2018 at 12:14:53PM -0700, Nick Terrell wrote: > Adds zstd support to crypto and scompress. Only supports the default > level. > > Previously we held off on this patch, since there weren't any users. > Now zram is ready for zstd support, but depends on CONFIG_CRYPTO_ZSTD, > which

Re: [PATCH] crypto : chtls_cm - Fix potential NULL pointer dereferences

On Tue, Apr 03, 2018 at 03:09:12PM -0500, Gustavo A. R. Silva wrote: > Add null checks on lookup_tid() return value in order to prevent > null pointer dereferences. > > Addresses-Coverity-ID: 1467422 ("Dereference null return value") > Addresses-Coverity-ID: 1467443 ("Dereference null return

Re: [PATCH v2 0/2] crypto: removing various VLAs

On Mon, Apr 09, 2018 at 03:54:45PM +0200, Salvatore Mesoraca wrote: > v2: > As suggested by Herbert Xu, the blocksize and alignmask checks > have been moved to crypto_check_alg. > So, now, all the other separate checks are not necessary. > Also, the defines have been moved

Re: [PATCH][next] crypto: chtls: remove redundant assignment to cdev->ports

On Fri, Apr 06, 2018 at 05:58:47PM +0100, Colin King wrote: > From: Colin Ian King > > There is a double assignment to cdev->ports, the first is redundant > as it is over-written so remove it. > > Detected by CoverityScan, CID#1467432 ("Unused value") > >

Re: [PATCH v2] crypto/ecc: Actually remove stack VLA usage

On Fri, Mar 30, 2018 at 09:55:44AM -0700, Kees Cook wrote: > On the quest to remove all VLAs from the kernel[1], this avoids VLAs > by just using the maximum allocation size (4 bytes) for stack arrays. > All the VLAs in ecc were either 3 or 4 bytes (or a multiple), so just > make it 4 bytes all

Re: [PATCH 2/2] cpufreq: brcmstb-avs-cpufreq: prefer SCMI cpufreq if supported

On 04/20/2018 02:35 AM, Viresh Kumar wrote: > On 20-04-18, 10:15, Sudeep Holla wrote: >> It still doesn't give the flexibility to switch between the two >> implementations boot time based on some firmware config(e.g. DT status >> property). > > I agree, but it didn't look like they need

Re: [PATCH v2 0/5] ThunderX ZIP driver bug fixes

On Mon, Apr 09, 2018 at 05:45:49PM +0200, Jan Glauber wrote: > Some bug fixes for this driver after it stopped working with virtual mapped > stacks. I think the first two patches qualify for stable. > > Jan Glauber (5): > crypto: thunderx_zip: Fix fallout from CONFIG_VMAP_STACK > crypto:

Re: [PATCH 1/2] mm: introduce memory.min

On 04/20/18 09:36, Roman Gushchin wrote: > --- > Documentation/cgroup-v2.txt | 20 + > include/linux/memcontrol.h | 15 ++- > include/linux/page_counter.h | 11 - > mm/memcontrol.c | 99 > > mm/page_counter.c

Re: [PATCH V2] USB: Increment wakeup count on remote wakeup.

On Fri, Apr 20, 2018 at 7:12 AM, Alan Stern wrote: > On Thu, 19 Apr 2018, Ravi Chandra Sadineni wrote: > >> On chromebooks we depend on wakeup count to identify the wakeup source. >> But currently USB devices do not increment the wakeup count when they >> trigger the

[PATCH 2/4] ALSA: usb-audio: ADC3: Fix channel mapping conversion for ADC3.

From: Michael Drake The channel mapping is defined by bChRelationship, not bChPurpose. Signed-off-by: Michael Drake --- sound/usb/stream.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/sound/usb/stream.c

[PATCH 3/4] ALSA: usb-audio: Use Class Specific EP for UAC3 devices.

bmAtributes offset doesn't exist in the UAC3 CS_EP descriptor. Hence, checking for pitch control as if it was UAC2 doesn't make any sense. Use the defined UAC3 offsets instead. Signed-off-by: Jorge Sanjuan --- sound/usb/stream.c | 17 +++-- 1 file

[PATCH 1/4] ALSA: usb-audio: UAC3. Add support for mixer unit.

This adds support for the MIXER UNIT in UAC3. All the information is obtained from the (HIGH CAPABILITY) Cluster's header. We don't read the rest of the logical cluster to obtain the channel config as that wont make any difference in the current mixer behaviour. The name of the mixer unit is not

[PATCH 4/6] virtio_console: drop custom control queue cleanup

We now cleanup all VQs on device removal - no need to handle the control VQ specially. Signed-off-by: Michael S. Tsirkin --- drivers/char/virtio_console.c | 17 - 1 file changed, 17 deletions(-) diff --git a/drivers/char/virtio_console.c

[PATCH 1/6] virtio_console: don't tie bufs to a vq

an allocated buffer doesn't need to be tied to a vq - only vq->vdev is ever used. Pass the function the just what it needs - the vdev. Signed-off-by: Michael S. Tsirkin --- drivers/char/virtio_console.c | 14 +++--- 1 file changed, 7 insertions(+), 7 deletions(-) diff

Re: [RFC] perf/core: what is exclude_idle supposed to do

On Fri, Apr 20, 2018 at 9:51 AM Vince Weaver wrote: > On Fri, 20 Apr 2018, Vince Weaver wrote: > > > AFAICT it works on Power and possibly ARM. > > > > at least some ARMs are a bit more honest about it than x86 > > > > ivybridge: > > Performance counter stats for

[PATCH 3/6] virtio_console: free buffers after reset

Console driver is out of spec. The spec says: A driver MUST NOT decrement the available idx on a live virtqueue (ie. there is no way to “unexpose” buffers). and it does exactly that by trying to detach unused buffers without doing a device reset first. Defer detaching the buffers

[PATCH 0/6] virtio-console: spec compliance fixes

Turns out virtio console tries to take a buffer out of an active vq. Works by sheer luck, and is explicitly forbidden by spec. And while going over it I saw that error handling is also broken - failure is easy to trigger if I force allocations to fail. Lightly tested. Michael S. Tsirkin (6):

Re: [PATCH v3 1/2] tracing: fix bad use of igrab in trace_uprobe.c

On Fri, 20 Apr 2018 09:56:24 -0700 Song Liu wrote: > s Miklos reported and suggested: > > This pattern repeats two times in trace_uprobe.c and in > kernel/events/core.c as well: > > ret = kern_path(filename, LOOKUP_FOLLOW, ); > if (ret) > goto

Re: [PATCH 1/3] lightnvm: pblk: rework write error recovery path

> On 19 Apr 2018, at 09.39, Hans Holmberg > wrote: > > From: Hans Holmberg > > The write error recovery path is incomplete, so rework > the write error recovery handling to do resubmits directly > from the write buffer. > > When a

[PATCH 1/4] sh: dreamcast: rtc: push down rtc class ops into driver

The dreamcast RTC support has an extra level of indirection to provide either the old read_persistent_clock/update_persistent_clock interface or the rtc-generic device for hctosys/systohc. Both do the same thing here, so we can do away with the abstraction and simply enable the RTC core code to

  1   2   3   4   5   6   7   8   9   10   >