Re: [PATCH] net: hamachi: use new api ethtool_{get|set}_link_ksettings

From: Philippe Reynes Date: Thu, 16 Feb 2017 22:46:14 +0100 > The ethtool api {get|set}_settings is deprecated. > We move this driver to new api {get|set}_link_ksettings. > > As I don't have the hardware, I'd be very pleased if > someone may test this patch. > >

Re: [PATCH] net: hamachi: use new api ethtool_{get|set}_link_ksettings

From: Philippe Reynes Date: Thu, 16 Feb 2017 22:46:14 +0100 > The ethtool api {get|set}_settings is deprecated. > We move this driver to new api {get|set}_link_ksettings. > > As I don't have the hardware, I'd be very pleased if > someone may test this patch. > > Signed-off-by: Philippe Reynes

Re: [PATCH] net: qlogic: netxen: use new api ethtool_{get|set}_link_ksettings

From: Philippe Reynes Date: Thu, 16 Feb 2017 23:28:01 +0100 > The ethtool api {get|set}_settings is deprecated. > We move this driver to new api {get|set}_link_ksettings. > > As I don't have the hardware, I'd be very pleased if > someone may test this patch. > >

Re: [PATCH] net: qlogic: netxen: use new api ethtool_{get|set}_link_ksettings

From: Philippe Reynes Date: Thu, 16 Feb 2017 23:28:01 +0100 > The ethtool api {get|set}_settings is deprecated. > We move this driver to new api {get|set}_link_ksettings. > > As I don't have the hardware, I'd be very pleased if > someone may test this patch. > > Signed-off-by: Philippe Reynes

Re: [RFC 1/1] shiftfs: uid/gid shifting bind mount

On Fri, Feb 17, 2017 at 09:24:40AM -0800, James Bottomley wrote: > > What happens when somebody comes along and creates the damn thing on > > the underlying fs? _Not_ via your code, that is - using the > > underlying fs mounted elsewhere. > > Point taken. This, I think fixes the dcache

Re: [RFC 1/1] shiftfs: uid/gid shifting bind mount

On Fri, Feb 17, 2017 at 09:24:40AM -0800, James Bottomley wrote: > > What happens when somebody comes along and creates the damn thing on > > the underlying fs? _Not_ via your code, that is - using the > > underlying fs mounted elsewhere. > > Point taken. This, I think fixes the dcache

Re: [PATCH v2] locking/pvqspinlock: Relax cmpxchg's to improve performance on some archs

On 02/12/2017 09:24 PM, panxinhui wrote: > > 在 2017/2/10 上午4:53, Waiman Long 写道: >> On 02/07/2017 10:39 PM, Xinhui Pan wrote: >>> >>> 2016-12-26 4:26 GMT+08:00 Waiman Long >> >: >>> >>> A number of cmpxchg calls in qspinlock_paravirt.h were

Re: [PATCH v2] locking/pvqspinlock: Relax cmpxchg's to improve performance on some archs

On 02/12/2017 09:24 PM, panxinhui wrote: > > 在 2017/2/10 上午4:53, Waiman Long 写道: >> On 02/07/2017 10:39 PM, Xinhui Pan wrote: >>> >>> 2016-12-26 4:26 GMT+08:00 Waiman Long >> >: >>> >>> A number of cmpxchg calls in qspinlock_paravirt.h were replaced by more >>>

[PATCH v2 3/3] staging: rtl8192u: Prefer using the BIT macro

Replaces left shift operation (1 << d) by BIT(x) macro. Fix the checkpatch.pl issue: CHECK: Prefer using the BIT macro replacing Signed-off-by: simran singhal --- V2: -modified patch message. drivers/staging/rtl8192u/ieee80211/ieee80211.h | 140

[PATCH v2 3/3] staging: rtl8192u: Prefer using the BIT macro

Replaces left shift operation (1 << d) by BIT(x) macro. Fix the checkpatch.pl issue: CHECK: Prefer using the BIT macro replacing Signed-off-by: simran singhal --- V2: -modified patch message. drivers/staging/rtl8192u/ieee80211/ieee80211.h | 140 - 1 file changed,

[PATCH v4] platform/x86: ideapad-laptop: Add sysfs interface for touchpad state

Lenovo Yoga (many variants: Yoga, Yoga2 Pro, Yoga2 13, Yoga3 Pro, Yoga 3 14 etc) has multiple modles that are a hybrid laptop, working in laptop mode as well as tablet mode. Currently, there is no easy interface to determine the touchpad status, which in case of the Yoga family of machines, can

[PATCH v4] platform/x86: ideapad-laptop: Add sysfs interface for touchpad state

Lenovo Yoga (many variants: Yoga, Yoga2 Pro, Yoga2 13, Yoga3 Pro, Yoga 3 14 etc) has multiple modles that are a hybrid laptop, working in laptop mode as well as tablet mode. Currently, there is no easy interface to determine the touchpad status, which in case of the Yoga family of machines, can

Re: [PATCH V2] perf: qcom: Add L3 cache PMU driver

On Thu, Feb 16, 2017 at 05:01:19PM -0500, Agustin Vega-Frias wrote: > On 2017-02-16 11:41, Mark Rutland wrote: > >On Thu, Feb 16, 2017 at 10:03:05AM -0500, Agustin Vega-Frias wrote: > >>This adds a new dynamic PMU to the Perf Events framework to program > >>and control the L3 cache PMUs in some

Re: [PATCH V2] perf: qcom: Add L3 cache PMU driver

On Thu, Feb 16, 2017 at 05:01:19PM -0500, Agustin Vega-Frias wrote: > On 2017-02-16 11:41, Mark Rutland wrote: > >On Thu, Feb 16, 2017 at 10:03:05AM -0500, Agustin Vega-Frias wrote: > >>This adds a new dynamic PMU to the Perf Events framework to program > >>and control the L3 cache PMUs in some

Re: net: use-after-free in tw_timer_handler

On Wed, Feb 8, 2017 at 9:36 AM, Dmitry Vyukov wrote: > On Tue, Jan 24, 2017 at 4:52 PM, Eric Dumazet wrote: >> On Tue, Jan 24, 2017 at 7:06 AM, Dmitry Vyukov wrote: This code was changed a long time ago :

Re: net: use-after-free in tw_timer_handler

On Wed, Feb 8, 2017 at 9:36 AM, Dmitry Vyukov wrote: > On Tue, Jan 24, 2017 at 4:52 PM, Eric Dumazet wrote: >> On Tue, Jan 24, 2017 at 7:06 AM, Dmitry Vyukov wrote: This code was changed a long time ago :

Re: [PATCH v3] Add sysfs interface for touchpad state

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 On Fri, 2017-02-17 at 18:12 +0200, Andy Shevchenko wrote: > > +static ssize_t touchpad_store(struct device *dev, > > +    struct device_attribute *attr, > > +    const char *buf, size_t count)

Re: [PATCH v3] Add sysfs interface for touchpad state

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 On Fri, 2017-02-17 at 18:12 +0200, Andy Shevchenko wrote: > > +static ssize_t touchpad_store(struct device *dev, > > +    struct device_attribute *attr, > > +    const char *buf, size_t count)

Re: [PATCH] tpm: Fix expected number of response bytes of TPM1.2 PCR Extend

On Fri, 2017-02-17 at 20:45 +0200, Jarkko Sakkinen wrote: > On Fri, Feb 17, 2017 at 07:46:38AM -0500, Mimi Zohar wrote: > > Hi James, > > > > On Wed, 2017-02-15 at 20:09 +0200, Jarkko Sakkinen wrote: > > > On Wed, Feb 15, 2017 at 11:56:23AM -0500, Stefan Berger wrote: > > > > The TPM1.2 PCR

Re: [PATCH] tpm: Fix expected number of response bytes of TPM1.2 PCR Extend

On Fri, 2017-02-17 at 20:45 +0200, Jarkko Sakkinen wrote: > On Fri, Feb 17, 2017 at 07:46:38AM -0500, Mimi Zohar wrote: > > Hi James, > > > > On Wed, 2017-02-15 at 20:09 +0200, Jarkko Sakkinen wrote: > > > On Wed, Feb 15, 2017 at 11:56:23AM -0500, Stefan Berger wrote: > > > > The TPM1.2 PCR

Re: [PATCH] driver core: unbind consumers before locking parent on device unbind

Am Freitag, den 17.02.2017, 10:42 -0800 schrieb Greg Kroah-Hartman: > On Fri, Feb 17, 2017 at 07:36:29PM +0100, Lucas Stach wrote: > > On forced unbind the parent lock is taken, as the device might be a USB > > device. The device to be unbound might have active consumers, which > > must be unbound

Re: [PATCH] driver core: unbind consumers before locking parent on device unbind

Am Freitag, den 17.02.2017, 10:42 -0800 schrieb Greg Kroah-Hartman: > On Fri, Feb 17, 2017 at 07:36:29PM +0100, Lucas Stach wrote: > > On forced unbind the parent lock is taken, as the device might be a USB > > device. The device to be unbound might have active consumers, which > > must be unbound

Re: [PATCH] tpm: Fix expected number of response bytes of TPM1.2 PCR Extend

On Fri, Feb 17, 2017 at 07:46:38AM -0500, Mimi Zohar wrote: > Hi James, > > On Wed, 2017-02-15 at 20:09 +0200, Jarkko Sakkinen wrote: > > On Wed, Feb 15, 2017 at 11:56:23AM -0500, Stefan Berger wrote: > > > The TPM1.2 PCR Extend operation only returns 20 bytes in the body, > > > which is the size

Re: [PATCH] tpm: Fix expected number of response bytes of TPM1.2 PCR Extend

On Fri, Feb 17, 2017 at 07:46:38AM -0500, Mimi Zohar wrote: > Hi James, > > On Wed, 2017-02-15 at 20:09 +0200, Jarkko Sakkinen wrote: > > On Wed, Feb 15, 2017 at 11:56:23AM -0500, Stefan Berger wrote: > > > The TPM1.2 PCR Extend operation only returns 20 bytes in the body, > > > which is the size

Re: [PATCH V3 3/7] mm: reclaim MADV_FREE pages

On Fri, Feb 17, 2017 at 11:01:54AM -0500, Johannes Weiner wrote: > On Thu, Feb 16, 2017 at 04:27:18PM -0800, Shaohua Li wrote: > > On Thu, Feb 16, 2017 at 01:40:18PM -0500, Johannes Weiner wrote: > > > On Tue, Feb 14, 2017 at 11:36:09AM -0800, Shaohua Li wrote: > > > > @@ -911,7 +911,7 @@ static

Re: [PATCH V3 3/7] mm: reclaim MADV_FREE pages

On Fri, Feb 17, 2017 at 11:01:54AM -0500, Johannes Weiner wrote: > On Thu, Feb 16, 2017 at 04:27:18PM -0800, Shaohua Li wrote: > > On Thu, Feb 16, 2017 at 01:40:18PM -0500, Johannes Weiner wrote: > > > On Tue, Feb 14, 2017 at 11:36:09AM -0800, Shaohua Li wrote: > > > > @@ -911,7 +911,7 @@ static

[PATCH] lockdep: Handle statically initialized PER_CPU locks proper

If a PER_CPU struct which contains a spin_lock is statically initialized via: DEFINE_PER_CPU(struct foo, bla) = { .lock = __SPIN_LOCK_UNLOCKED(bla.lock) }; then lockdep assigns a seperate key to each lock because the logic for assigning a key to statically initialized locks is to use the

[PATCH] lockdep: Handle statically initialized PER_CPU locks proper

If a PER_CPU struct which contains a spin_lock is statically initialized via: DEFINE_PER_CPU(struct foo, bla) = { .lock = __SPIN_LOCK_UNLOCKED(bla.lock) }; then lockdep assigns a seperate key to each lock because the logic for assigning a key to statically initialized locks is to use the

Re: v4.10-rc8 (-rc6) boot regression on Intel desktop, does not boot after cold boots, boots after reboot

On Fri, Feb 17, 2017 at 06:05:08PM +0100, Pavel Machek wrote: > On Fri 2017-02-17 17:37:47, Thomas Gleixner wrote: > > On Fri, 17 Feb 2017, Frederic Weisbecker wrote: > > > On Thu, Feb 16, 2017 at 08:34:45PM +0100, Thomas Gleixner wrote: > > > > On Thu, 16 Feb 2017, Frederic Weisbecker wrote: > >

Re: v4.10-rc8 (-rc6) boot regression on Intel desktop, does not boot after cold boots, boots after reboot

On Fri, Feb 17, 2017 at 06:05:08PM +0100, Pavel Machek wrote: > On Fri 2017-02-17 17:37:47, Thomas Gleixner wrote: > > On Fri, 17 Feb 2017, Frederic Weisbecker wrote: > > > On Thu, Feb 16, 2017 at 08:34:45PM +0100, Thomas Gleixner wrote: > > > > On Thu, 16 Feb 2017, Frederic Weisbecker wrote: > >

Re: [PATCH] staging: bcm2835-audio: bcm2835.h: fix various coding style issues

On Fri, Feb 17, 2017 at 01:39:07PM -0500, Nathan Howard wrote: > The following coding style issues (as per checkpatch.pl) were resolved. > > WARNING: Block comments use * on subsequent lines > WARNING: Prefer [subsystem eg: netdev]_info([subsystem]dev, ... > WARNING: Missing a blank line after

Re: [PATCH] staging: bcm2835-audio: bcm2835.h: fix various coding style issues

On Fri, Feb 17, 2017 at 01:39:07PM -0500, Nathan Howard wrote: > The following coding style issues (as per checkpatch.pl) were resolved. > > WARNING: Block comments use * on subsequent lines > WARNING: Prefer [subsystem eg: netdev]_info([subsystem]dev, ... > WARNING: Missing a blank line after

Re: swap_cluster_info lockdep splat

On Fri, 17 Feb 2017, Huang, Ying wrote: > > I found a memory leak in __read_swap_cache_async() introduced by mm-swap > series, and confirmed it via testing. Could you verify whether it fixed > your cases? Thanks a lot for reporting. Well caught! That indeed fixes the leak I've been seeing: my

Re: swap_cluster_info lockdep splat

On Fri, 17 Feb 2017, Huang, Ying wrote: > > I found a memory leak in __read_swap_cache_async() introduced by mm-swap > series, and confirmed it via testing. Could you verify whether it fixed > your cases? Thanks a lot for reporting. Well caught! That indeed fixes the leak I've been seeing: my

Re: [PATCH] driver core: unbind consumers before locking parent on device unbind

On Fri, Feb 17, 2017 at 07:36:29PM +0100, Lucas Stach wrote: > On forced unbind the parent lock is taken, as the device might be a USB > device. The device to be unbound might have active consumers, which > must be unbound before calling device_release_driver(), otherwise this > function might

Re: [PATCH] driver core: unbind consumers before locking parent on device unbind

On Fri, Feb 17, 2017 at 07:36:29PM +0100, Lucas Stach wrote: > On forced unbind the parent lock is taken, as the device might be a USB > device. The device to be unbound might have active consumers, which > must be unbound before calling device_release_driver(), otherwise this > function might

Re: [PATCH v9] soc: qcom: Add SoC info driver

On Thu 16 Feb 02:45 PST 2017, Imran Khan wrote: > The SoC info driver provides information such as Chip ID, > Chip family, serial number and other such details about > Qualcomm SoCs to user space, so that if needed some user > space utility(like antutu) can query such information > using sysfs

Re: [PATCH v9] soc: qcom: Add SoC info driver

On Thu 16 Feb 02:45 PST 2017, Imran Khan wrote: > The SoC info driver provides information such as Chip ID, > Chip family, serial number and other such details about > Qualcomm SoCs to user space, so that if needed some user > space utility(like antutu) can query such information > using sysfs

[PATCH] staging: bcm2835-audio: bcm2835.h: fix various coding style issues

The following coding style issues (as per checkpatch.pl) were resolved. WARNING: Block comments use * on subsequent lines WARNING: Prefer [subsystem eg: netdev]_info([subsystem]dev, ... WARNING: Missing a blank line after declarations WARNING: Use of volatile is usually wrong:... WARNING: line

[PATCH] staging: bcm2835-audio: bcm2835.h: fix various coding style issues

The following coding style issues (as per checkpatch.pl) were resolved. WARNING: Block comments use * on subsequent lines WARNING: Prefer [subsystem eg: netdev]_info([subsystem]dev, ... WARNING: Missing a blank line after declarations WARNING: Use of volatile is usually wrong:... WARNING: line

Re: [PATCH 2/2] f2fs: fix the case when there is no free segment to allocate for CURSEG_WARM_NODE

Hi Yunlong, I already started to test this since a couple of days ago. :) http://git.kernel.org/cgit/linux/kernel/git/jaegeuk/f2fs.git/commit/?h=dev-test=908b5f463c82eaf972b149a26bb310f5e25064fd Thanks, On 02/17, Yunlong Song wrote: > If the free segments are used up, then new_curseg will fail

Re: [PATCH 2/2] f2fs: fix the case when there is no free segment to allocate for CURSEG_WARM_NODE

Hi Yunlong, I already started to test this since a couple of days ago. :) http://git.kernel.org/cgit/linux/kernel/git/jaegeuk/f2fs.git/commit/?h=dev-test=908b5f463c82eaf972b149a26bb310f5e25064fd Thanks, On 02/17, Yunlong Song wrote: > If the free segments are used up, then new_curseg will fail

[PATCH] driver core: unbind consumers before locking parent on device unbind

On forced unbind the parent lock is taken, as the device might be a USB device. The device to be unbound might have active consumers, which must be unbound before calling device_release_driver(), otherwise this function might deadlock when trying to take the parent lock during consumer unbind.

[PATCH] driver core: unbind consumers before locking parent on device unbind

On forced unbind the parent lock is taken, as the device might be a USB device. The device to be unbound might have active consumers, which must be unbound before calling device_release_driver(), otherwise this function might deadlock when trying to take the parent lock during consumer unbind.

Re: [PATCH v8 2/2] Documentation/ABI: Add ABI information for QCOM socinfo driver

On Tue 10 Jan 07:48 PST 2017, Imran Khan wrote: > + > +What:/sys/devices/soc0/machine > +Date:January 2017 > +Description: > + This file shows the machine name as given in the DT. This description needs to be updated. [..] > + > +What:

Re: [PATCH v8 2/2] Documentation/ABI: Add ABI information for QCOM socinfo driver

On Tue 10 Jan 07:48 PST 2017, Imran Khan wrote: > + > +What:/sys/devices/soc0/machine > +Date:January 2017 > +Description: > + This file shows the machine name as given in the DT. This description needs to be updated. [..] > + > +What:

Re: [RFC 1/2] fs,eventpoll: Add ability to install target file by its number

On 02/17/2017 01:01 PM, Cyrill Gorcunov wrote: On Fri, Feb 17, 2017 at 09:20:34AM -0800, Andy Lutomirski wrote: This is a scary thing to let an unprivileged process do. I'm wondering if there might be a nicer way to address this using a better interface in /proc. Well, I tend to agree.

Re: [RFC 1/2] fs,eventpoll: Add ability to install target file by its number

On 02/17/2017 01:01 PM, Cyrill Gorcunov wrote: On Fri, Feb 17, 2017 at 09:20:34AM -0800, Andy Lutomirski wrote: This is a scary thing to let an unprivileged process do. I'm wondering if there might be a nicer way to address this using a better interface in /proc. Well, I tend to agree.

[PATCH] MAINTAINERS: cpufreq: add bmips-cpufreq.c

From: Markus Mayer Add maintainer information for bmips-cpufreq.c. Signed-off-by: Markus Mayer --- This is based on PM's linux-next from today (February 17). This patch could be squashed into patch 3/4 of the original series if that is acceptable

[PATCH] MAINTAINERS: cpufreq: add bmips-cpufreq.c

From: Markus Mayer Add maintainer information for bmips-cpufreq.c. Signed-off-by: Markus Mayer --- This is based on PM's linux-next from today (February 17). This patch could be squashed into patch 3/4 of the original series if that is acceptable (see [1]) or it can remain separate. [1]

systemtap 3.1 release

The SystemTap team announces release 3.1! Highlights include syscall probes default to non-dwarf fallback, python function probes, @variance and statistics optimizations, java probe argument generalization, and user-space value-setting functions. = Where to get it

systemtap 3.1 release

The SystemTap team announces release 3.1! Highlights include syscall probes default to non-dwarf fallback, python function probes, @variance and statistics optimizations, java probe argument generalization, and user-space value-setting functions. = Where to get it

[PATCH] f2fs: trace victim's cost selectecd by f2fs_gc

This patch adds min_cost of each victims. Signed-off-by: Jaegeuk Kim --- include/trace/events/f2fs.h | 8 ++-- 1 file changed, 6 insertions(+), 2 deletions(-) diff --git a/include/trace/events/f2fs.h b/include/trace/events/f2fs.h index 153572e256d6..ff31ccfb8111 100644

[PATCH] f2fs: trace victim's cost selectecd by f2fs_gc

This patch adds min_cost of each victims. Signed-off-by: Jaegeuk Kim --- include/trace/events/f2fs.h | 8 ++-- 1 file changed, 6 insertions(+), 2 deletions(-) diff --git a/include/trace/events/f2fs.h b/include/trace/events/f2fs.h index 153572e256d6..ff31ccfb8111 100644 ---

Re: [PATCH v4 23/36] media: imx: Add MIPI CSI-2 Receiver subdev driver

On 02/17/2017 06:16 AM, Philipp Zabel wrote: On Fri, 2017-02-17 at 11:47 +0100, Philipp Zabel wrote: On Wed, 2017-02-15 at 18:19 -0800, Steve Longerbeam wrote: +static void csi2_dphy_init(struct csi2_dev *csi2) +{ + /* +* FIXME: 0x14 is derived from a fixed D-PHY reference +

Re: [PATCH v4 23/36] media: imx: Add MIPI CSI-2 Receiver subdev driver

On 02/17/2017 06:16 AM, Philipp Zabel wrote: On Fri, 2017-02-17 at 11:47 +0100, Philipp Zabel wrote: On Wed, 2017-02-15 at 18:19 -0800, Steve Longerbeam wrote: +static void csi2_dphy_init(struct csi2_dev *csi2) +{ + /* +* FIXME: 0x14 is derived from a fixed D-PHY reference +

[PATCH] watchdog: softdog: fire watchdog even if softirqs do not get to run

From: Niklas Cassel Checking for timer expiration is done from the softirq TIMER_SOFTIRQ. Since commit 4cd13c21b207 ("softirq: Let ksoftirqd do its job"), pending softirqs are no longer always handled immediately, instead, if there are pending softirqs, and ksoftirqd is

[PATCH] watchdog: softdog: fire watchdog even if softirqs do not get to run

From: Niklas Cassel Checking for timer expiration is done from the softirq TIMER_SOFTIRQ. Since commit 4cd13c21b207 ("softirq: Let ksoftirqd do its job"), pending softirqs are no longer always handled immediately, instead, if there are pending softirqs, and ksoftirqd is in state TASK_RUNNING,

Re: [PATCH v2 07/10] mm, compaction: restrict async compaction to pageblocks of same migratetype

On Fri, Feb 17, 2017 at 05:32:00PM +0100, Vlastimil Babka wrote: > On 02/14/2017 09:10 PM, Johannes Weiner wrote: > > On Fri, Feb 10, 2017 at 06:23:40PM +0100, Vlastimil Babka wrote: > >> The migrate scanner in async compaction is currently limited to > >> MIGRATE_MOVABLE > >> pageblocks. This is

Re: [PATCH v2 07/10] mm, compaction: restrict async compaction to pageblocks of same migratetype

On Fri, Feb 17, 2017 at 05:32:00PM +0100, Vlastimil Babka wrote: > On 02/14/2017 09:10 PM, Johannes Weiner wrote: > > On Fri, Feb 10, 2017 at 06:23:40PM +0100, Vlastimil Babka wrote: > >> The migrate scanner in async compaction is currently limited to > >> MIGRATE_MOVABLE > >> pageblocks. This is

Re: [PATCHv3 2/2] arch: Rename CONFIG_DEBUG_RODATA and CONFIG_DEBUG_MODULE_RONX

On Thu, Feb 16, 2017 at 05:08:20PM -0800, Kees Cook wrote: > On Thu, Feb 16, 2017 at 2:25 PM, Pavel Machek wrote: > > Hi! > > > >> > >> -config DEBUG_RODATA > >> +config STRICT_KERNEL_RWX > >> bool "Make kernel text and rodata read-only" if > >> ARCH_OPTIONAL_KERNEL_RWX > >>

Re: [PATCHv3 2/2] arch: Rename CONFIG_DEBUG_RODATA and CONFIG_DEBUG_MODULE_RONX

On Thu, Feb 16, 2017 at 05:08:20PM -0800, Kees Cook wrote: > On Thu, Feb 16, 2017 at 2:25 PM, Pavel Machek wrote: > > Hi! > > > >> > >> -config DEBUG_RODATA > >> +config STRICT_KERNEL_RWX > >> bool "Make kernel text and rodata read-only" if > >> ARCH_OPTIONAL_KERNEL_RWX > >> depends

Re: [PATCH] Documentation: Note QDF2400 SoC Erratum 44

On Wed, Feb 15, 2017 at 04:54:07PM -0500, Christopher Covington wrote: > The Qualcomm Datacenter Technologies QDF2400 family of SoCs contains a > custom (non-PrimeCell) implementation of the SBSA UART. Occasionally the > BUSY bit in the Flag Register gets stuck as 1, erratum 44 for both 2432v1 >

Re: [PATCH] Documentation: Note QDF2400 SoC Erratum 44

On Wed, Feb 15, 2017 at 04:54:07PM -0500, Christopher Covington wrote: > The Qualcomm Datacenter Technologies QDF2400 family of SoCs contains a > custom (non-PrimeCell) implementation of the SBSA UART. Occasionally the > BUSY bit in the Flag Register gets stuck as 1, erratum 44 for both 2432v1 >

[PATCH] fs: switch order of CAP_DAC_OVERRIDE and CAP_DAC_READ_SEARCH checks

generic_permission() presently checks CAP_DAC_OVERRIDE prior to CAP_DAC_READ_SEARCH. This can cause misleading audit messages when using a LSM such as SELinux or AppArmor, since CAP_DAC_OVERRIDE may not be required for the operation. Flip the order of the tests so that CAP_DAC_OVERRIDE is only

[PATCH] fs: switch order of CAP_DAC_OVERRIDE and CAP_DAC_READ_SEARCH checks

generic_permission() presently checks CAP_DAC_OVERRIDE prior to CAP_DAC_READ_SEARCH. This can cause misleading audit messages when using a LSM such as SELinux or AppArmor, since CAP_DAC_OVERRIDE may not be required for the operation. Flip the order of the tests so that CAP_DAC_OVERRIDE is only

[PATCH net-next] rxrpc: Change module filename to rxrpc.ko

Change module filename from af-rxrpc.ko to rxrpc.ko so as to be consistent with the other protocol drivers. Also adjust the documentation to reflect this. Further, there is no longer a standalone rxkad module, as it has been merged into the rxrpc core, so get rid of references to that.

[PATCH net-next] rxrpc: Change module filename to rxrpc.ko

Change module filename from af-rxrpc.ko to rxrpc.ko so as to be consistent with the other protocol drivers. Also adjust the documentation to reflect this. Further, there is no longer a standalone rxkad module, as it has been merged into the rxrpc core, so get rid of references to that.

Re: Hard-coding PTY device node numbers in userspace

On Fri, Feb 17, 2017 at 12:02:52PM +0100, Florian Weimer wrote: > We want to reject PTY devices from other namespaces as valid input to > the ttyname and ttyname_r functions, while still providing a hint to > callers that the device is, in fact, a PTY. Christian Brauner wrote a > glibc patch for

Re: Hard-coding PTY device node numbers in userspace

On Fri, Feb 17, 2017 at 12:02:52PM +0100, Florian Weimer wrote: > We want to reject PTY devices from other namespaces as valid input to > the ttyname and ttyname_r functions, while still providing a hint to > callers that the device is, in fact, a PTY. Christian Brauner wrote a > glibc patch for

Re: [PATCHv2 4/5] perf stat: Add -a as a default target

On February 17, 2017 6:00:34 PM GMT+01:00, Jiri Olsa wrote: >--- >Boris asked for default -a option in case we monitor >only uncore events. While implementing that I thought >it might be actually useful to make it overall default. > >Running 'perf stat' will now collect system

Re: [PATCHv2 4/5] perf stat: Add -a as a default target

On February 17, 2017 6:00:34 PM GMT+01:00, Jiri Olsa wrote: >--- >Boris asked for default -a option in case we monitor >only uncore events. While implementing that I thought >it might be actually useful to make it overall default. > >Running 'perf stat' will now collect system wide data. >

Re: [PATCH 4.9 00/32] 4.9.11-stable review

On Fri, Feb 17, 2017 at 02:38:10AM -0800, Guenter Roeck wrote: > On 02/16/2017 09:54 AM, Greg Kroah-Hartman wrote: > > This is the start of the stable review cycle for the 4.9.11 release. > > There are 32 patches in this series, all will be posted as a response > > to this one. If anyone has any

Re: [PATCH 4.9 00/32] 4.9.11-stable review

On Fri, Feb 17, 2017 at 02:38:10AM -0800, Guenter Roeck wrote: > On 02/16/2017 09:54 AM, Greg Kroah-Hartman wrote: > > This is the start of the stable review cycle for the 4.9.11 release. > > There are 32 patches in this series, all will be posted as a response > > to this one. If anyone has any

Re: [RFC 1/2] fs,eventpoll: Add ability to install target file by its number

On Fri, Feb 17, 2017 at 09:20:34AM -0800, Andy Lutomirski wrote: > >> > >> This is a scary thing to let an unprivileged process do. > >> > >> I'm wondering if there might be a nicer way to address this using a > >> better interface in /proc. > > > > Well, I tend to agree. Need to add security

Re: [RFC 1/2] fs,eventpoll: Add ability to install target file by its number

On Fri, Feb 17, 2017 at 09:20:34AM -0800, Andy Lutomirski wrote: > >> > >> This is a scary thing to let an unprivileged process do. > >> > >> I'm wondering if there might be a nicer way to address this using a > >> better interface in /proc. > > > > Well, I tend to agree. Need to add security

Re: pull-request: wireless-drivers-next 2017-02-17

From: Kalle Valo Date: Thu, 16 Feb 2017 15:41:13 +0200 > few -next patches I'm still hoping to get to 4.11 to keep my backlog > short, nothing major here. Please let me know if there are any problems. Pulled, thanks Kalle.

Re: pull-request: wireless-drivers-next 2017-02-17

From: Kalle Valo Date: Thu, 16 Feb 2017 15:41:13 +0200 > few -next patches I'm still hoping to get to 4.11 to keep my backlog > short, nothing major here. Please let me know if there are any problems. Pulled, thanks Kalle.

Re: [PATCH v2 0/3] x86/vdso: Add Hyper-V TSC page clocksource support

On Fri, 17 Feb 2017, Andy Lutomirski wrote: > On Fri, Feb 17, 2017 at 2:14 AM, Vitaly Kuznetsov wrote: > > Not only. As far as I understand (and I *think* K. Y. pointed this out) > > when VM is migrating to another host TSC page clocksource is disabled for > > extended period

Re: [PATCH v2 0/3] x86/vdso: Add Hyper-V TSC page clocksource support

On Fri, 17 Feb 2017, Andy Lutomirski wrote: > On Fri, Feb 17, 2017 at 2:14 AM, Vitaly Kuznetsov wrote: > > Not only. As far as I understand (and I *think* K. Y. pointed this out) > > when VM is migrating to another host TSC page clocksource is disabled for > > extended period of time so we're

Re: [PATCH] pci-hyperv: Use device serial number as PCI domain

On Mon, 13 Feb 2017 18:10:11 + Haiyang Zhang wrote: > This allows PCI domain numbers starts with 1, and also unique > on the same VM. So names, such as VF NIC names, that include > domain number as part of the name, can be shorter than that > based on part of bus UUID

Re: [PATCH] pci-hyperv: Use device serial number as PCI domain

On Mon, 13 Feb 2017 18:10:11 + Haiyang Zhang wrote: > This allows PCI domain numbers starts with 1, and also unique > on the same VM. So names, such as VF NIC names, that include > domain number as part of the name, can be shorter than that > based on part of bus UUID previously. The new

Re: [RFC 4/8] doc: fpga-mgr: separate getting/locking FPGA manager

Alan, small nits inline On Wed, Feb 15, 2017 at 8:14 AM, Alan Tull wrote: > Document that getting a reference to a FPGA Manager has been > separated from locking the FPGA Mangager for use. > > fpga_mgr_lock/unlock functions get/release mutex. > > of_fpga_mgr_get, fpga_mgr_get,

Re: [RFC 4/8] doc: fpga-mgr: separate getting/locking FPGA manager

Alan, small nits inline On Wed, Feb 15, 2017 at 8:14 AM, Alan Tull wrote: > Document that getting a reference to a FPGA Manager has been > separated from locking the FPGA Mangager for use. > > fpga_mgr_lock/unlock functions get/release mutex. > > of_fpga_mgr_get, fpga_mgr_get, and fpga_mgr_put

Re: [PATCH] groups: don't return unmapped gids in getgroups(2)

One thing overlooked by commit 9cc46516ddf4 ("userns: Add a knob to disable setgroups on a per user namespace basis") is that because setgroups(2) no longer works in user namespaces it doesn't make any sense to be returning weird group IDs that the process cannot do

Re: [PATCH] groups: don't return unmapped gids in getgroups(2)

One thing overlooked by commit 9cc46516ddf4 ("userns: Add a knob to disable setgroups on a per user namespace basis") is that because setgroups(2) no longer works in user namespaces it doesn't make any sense to be returning weird group IDs that the process cannot do

Re: [RFC 1/1] shiftfs: uid/gid shifting bind mount

On Fri, 2017-02-17 at 02:55 +, Al Viro wrote: > On Thu, Feb 16, 2017 at 07:56:30AM -0800, James Bottomley wrote: > > > > Hi James, > > > > > > Should it be "return d_splice_alias()" so that if we find an > > > alias it is returned back to caller and passed in dentry can be > > > freed.

Re: [RFC 1/1] shiftfs: uid/gid shifting bind mount

On Fri, 2017-02-17 at 02:55 +, Al Viro wrote: > On Thu, Feb 16, 2017 at 07:56:30AM -0800, James Bottomley wrote: > > > > Hi James, > > > > > > Should it be "return d_splice_alias()" so that if we find an > > > alias it is returned back to caller and passed in dentry can be > > > freed.

Re: [PATCH] arm64: traps: Mark __le16, __le32, __user variables properly

On Fri, Feb 17, 2017 at 08:51:12AM -0800, Stephen Boyd wrote: > diff --git a/arch/arm64/kernel/traps.c b/arch/arm64/kernel/traps.c > index 659b2e6b6cf7..23959cb70ded 100644 > --- a/arch/arm64/kernel/traps.c > +++ b/arch/arm64/kernel/traps.c > @@ -84,7 +84,7 @@ static void dump_mem(const char *lvl,

Re: [PATCH] arm64: traps: Mark __le16, __le32, __user variables properly

On Fri, Feb 17, 2017 at 08:51:12AM -0800, Stephen Boyd wrote: > diff --git a/arch/arm64/kernel/traps.c b/arch/arm64/kernel/traps.c > index 659b2e6b6cf7..23959cb70ded 100644 > --- a/arch/arm64/kernel/traps.c > +++ b/arch/arm64/kernel/traps.c > @@ -84,7 +84,7 @@ static void dump_mem(const char *lvl,

Re: [PATCH] KVM: x86: remove code for lazy FPU handling

Paolo Bonzini writes: > On 17/02/2017 01:45, Bandan Das wrote: >> Paolo Bonzini writes: >> >>> The FPU is always active now when running KVM. >> >> The lazy code was a performance optimization, correct ? >> Is this just dormant code and being removed

Re: [PATCH] KVM: x86: remove code for lazy FPU handling

Paolo Bonzini writes: > On 17/02/2017 01:45, Bandan Das wrote: >> Paolo Bonzini writes: >> >>> The FPU is always active now when running KVM. >> >> The lazy code was a performance optimization, correct ? >> Is this just dormant code and being removed ? Maybe >> mentioning the reasoning in a

Re: [RFC 1/1] shiftfs: uid/gid shifting bind mount

On Fri, 2017-02-17 at 02:29 +, Al Viro wrote: > On Sat, Feb 04, 2017 at 11:19:32AM -0800, James Bottomley wrote: > > > +static const struct dentry_operations shiftfs_dentry_ops = { > > + .d_release = shiftfs_d_release, > > + .d_real = shiftfs_d_real, > > +}; > > In other

Re: [RFC 1/1] shiftfs: uid/gid shifting bind mount

On Fri, 2017-02-17 at 02:29 +, Al Viro wrote: > On Sat, Feb 04, 2017 at 11:19:32AM -0800, James Bottomley wrote: > > > +static const struct dentry_operations shiftfs_dentry_ops = { > > + .d_release = shiftfs_d_release, > > + .d_real = shiftfs_d_real, > > +}; > > In other

Re: kmemleak splat on copy_process()

On Fri, Feb 17, 2017 at 9:07 AM, Andy Lutomirski wrote: > But maybe > there really is a race in which a kmemleak check right in the middle > of duplicating the task struct really can't see the stack pointer. Funny, but it was actually using kmemleak how I can easily

Re: kmemleak splat on copy_process()

On Fri, Feb 17, 2017 at 9:07 AM, Andy Lutomirski wrote: > But maybe > there really is a race in which a kmemleak check right in the middle > of duplicating the task struct really can't see the stack pointer. Funny, but it was actually using kmemleak how I can easily reproduce: To reproduce the

Re: [PATCH] KVM: VMX: use vmcs_set/clear_bits for CPU-based execution controls

Paolo Bonzini writes: > - Original Message - >> From: "Bandan Das" >> To: "Paolo Bonzini" >> Cc: linux-kernel@vger.kernel.org, k...@vger.kernel.org >> Sent: Friday, February 17, 2017 1:04:14 AM >> Subject: Re: [PATCH] KVM: VMX:

Re: [PATCH] KVM: VMX: use vmcs_set/clear_bits for CPU-based execution controls

Paolo Bonzini writes: > - Original Message - >> From: "Bandan Das" >> To: "Paolo Bonzini" >> Cc: linux-kernel@vger.kernel.org, k...@vger.kernel.org >> Sent: Friday, February 17, 2017 1:04:14 AM >> Subject: Re: [PATCH] KVM: VMX: use vmcs_set/clear_bits for CPU-based >> execution

Re: [PATCHv3 33/33] mm, x86: introduce PR_SET_MAX_VADDR and PR_GET_MAX_VADDR

On Fri, Feb 17, 2017 at 9:19 AM, Dave Hansen wrote: > On 02/17/2017 06:13 AM, Kirill A. Shutemov wrote: >> +/* >> + * Default maximum virtual address. This is required for >> + * compatibility with applications that assumes 47-bit VA. >> + * The limit can be changed with

Re: [PATCHv3 33/33] mm, x86: introduce PR_SET_MAX_VADDR and PR_GET_MAX_VADDR

On Fri, Feb 17, 2017 at 9:19 AM, Dave Hansen wrote: > On 02/17/2017 06:13 AM, Kirill A. Shutemov wrote: >> +/* >> + * Default maximum virtual address. This is required for >> + * compatibility with applications that assumes 47-bit VA. >> + * The limit can be changed with prctl(PR_SET_MAX_VADDR).

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