RE: [PATCH V5 4/8] perf/x86/intel/uncore: add new data structures for free running counters

> On Fri, Jan 19, 2018 at 03:15:00PM +, Liang, Kan wrote: > > > > > > On Thu, Jan 18, 2018 at 05:43:10PM +, Liang, Kan wrote: > > > > In the uncore document, there is no event-code assigned to free > > > > running > > > counters. > > > > Some events need to be defined to indicate the free

RE: [PATCH V5 4/8] perf/x86/intel/uncore: add new data structures for free running counters

> On Fri, Jan 19, 2018 at 03:15:00PM +, Liang, Kan wrote: > > > > > > On Thu, Jan 18, 2018 at 05:43:10PM +, Liang, Kan wrote: > > > > In the uncore document, there is no event-code assigned to free > > > > running > > > counters. > > > > Some events need to be defined to indicate the free

Re: [PATCH] general protection fault in sock_has_perm

On 01/19/2018 09:06 AM, Paul Moore wrote: On Fri, Jan 19, 2018 at 10:49 AM, Mark Salyzyn wrote: On 01/18/2018 02:36 PM, Paul Moore wrote: On Thu, Jan 18, 2018 at 4:58 PM, Mark Salyzyn wrote: general protection fault: [#1] PREEMPT SMP KASAN CPU:

Re: [PATCH] general protection fault in sock_has_perm

On 01/19/2018 09:06 AM, Paul Moore wrote: On Fri, Jan 19, 2018 at 10:49 AM, Mark Salyzyn wrote: On 01/18/2018 02:36 PM, Paul Moore wrote: On Thu, Jan 18, 2018 at 4:58 PM, Mark Salyzyn wrote: general protection fault: [#1] PREEMPT SMP KASAN CPU: 1 PID: 14233 Comm: syz-executor2 Not

Re: [tip:sched/core] sched/rt: Simplify the IPI based RT balancing logic

On Fri, Jan 19, 2018 at 10:03:53AM -0500, Steven Rostedt wrote: > On Fri, 19 Jan 2018 14:53:05 +0530 > Pavan Kondeti wrote: > > > I am seeing "spinlock already unlocked" BUG for rd->rto_lock on a 4.9 > > stable kernel based system. This issue is observed only after > >

Re: [tip:sched/core] sched/rt: Simplify the IPI based RT balancing logic

On Fri, Jan 19, 2018 at 10:03:53AM -0500, Steven Rostedt wrote: > On Fri, 19 Jan 2018 14:53:05 +0530 > Pavan Kondeti wrote: > > > I am seeing "spinlock already unlocked" BUG for rd->rto_lock on a 4.9 > > stable kernel based system. This issue is observed only after > > inclusion of this patch.

[PATCH] kasan: add __asan_report_loadN/storeN_noabort callbacks

Instead of __asan_report_load_n_noabort and __asan_report_store_n_noabort callbacks Clang emits differently named __asan_report_loadN_noabort and __asan_report_storeN_noabort (similar to __asan_loadN/storeN_noabort, whose names both GCC and Clang agree on). Add callback implementation for

[PATCH] kasan: add __asan_report_loadN/storeN_noabort callbacks

Instead of __asan_report_load_n_noabort and __asan_report_store_n_noabort callbacks Clang emits differently named __asan_report_loadN_noabort and __asan_report_storeN_noabort (similar to __asan_loadN/storeN_noabort, whose names both GCC and Clang agree on). Add callback implementation for

[PATCH 0/2] [GIT PULL] tracing: A couple more small fixes for 4.15

Linus, Two more small fixes - The conversion of enums into their actual numbers to display in the event format file had an off-by-one bug, that could cause an enum not to be converted, and break user space parsing tools. - A fix to a previous fix to bring back the context recursion

[PATCH 0/2] [GIT PULL] tracing: A couple more small fixes for 4.15

Linus, Two more small fixes - The conversion of enums into their actual numbers to display in the event format file had an off-by-one bug, that could cause an enum not to be converted, and break user space parsing tools. - A fix to a previous fix to bring back the context recursion

[git pull] Input updates for v4.15-rc8

Hi Linus, Please pull from: git://git.kernel.org/pub/scm/linux/kernel/git/dtor/input.git for-linus to receive updates for the input subsystem. You will get: - a fix for use-after-free in Synaptics RMI4 driver - correction to multitouch contact tracking on certain ALPS touchpads

[git pull] Input updates for v4.15-rc8

Hi Linus, Please pull from: git://git.kernel.org/pub/scm/linux/kernel/git/dtor/input.git for-linus to receive updates for the input subsystem. You will get: - a fix for use-after-free in Synaptics RMI4 driver - correction to multitouch contact tracking on certain ALPS touchpads

[PATCH 2/2] tracing: Fix converting enums from the map in trace_event_eval_update()

From: "Steven Rostedt (VMware)" Since enums do not get converted by the TRACE_EVENT macro into their values, the event format displaces the enum name and not the value. This breaks tools like perf and trace-cmd that need to interpret the raw binary data. To solve this, an

[PATCH 2/2] tracing: Fix converting enums from the map in trace_event_eval_update()

From: "Steven Rostedt (VMware)" Since enums do not get converted by the TRACE_EVENT macro into their values, the event format displaces the enum name and not the value. This breaks tools like perf and trace-cmd that need to interpret the raw binary data. To solve this, an enum map was created to

[PATCH 1/2] ring-buffer: Fix duplicate results in mapping context to bits in recursive lock

From: "Steven Rostedt (VMware)" In bringing back the context checks, the code checks first if its normal (non-interrupt) context, and then for NMI then IRQ then softirq. The final check is redundant. Since the if branch is only hit if the context is one of NMI, IRQ, or

[PATCH 1/2] ring-buffer: Fix duplicate results in mapping context to bits in recursive lock

From: "Steven Rostedt (VMware)" In bringing back the context checks, the code checks first if its normal (non-interrupt) context, and then for NMI then IRQ then softirq. The final check is redundant. Since the if branch is only hit if the context is one of NMI, IRQ, or SOFTIRQ, if it's not NMI

Re: [PATCH] general protection fault in sock_has_perm

On Fri, 2018-01-19 at 12:19 -0500, Stephen Smalley wrote: > On Thu, 2018-01-18 at 13:58 -0800, Mark Salyzyn wrote: > > general protection fault: [#1] PREEMPT SMP KASAN > > CPU: 1 PID: 14233 Comm: syz-executor2 Not tainted 4.4.112-g5f6325b > > #28 > > task: 8801d1095f00 task.stack:

Re: [PATCH] general protection fault in sock_has_perm

On Fri, 2018-01-19 at 12:19 -0500, Stephen Smalley wrote: > On Thu, 2018-01-18 at 13:58 -0800, Mark Salyzyn wrote: > > general protection fault: [#1] PREEMPT SMP KASAN > > CPU: 1 PID: 14233 Comm: syz-executor2 Not tainted 4.4.112-g5f6325b > > #28 > > task: 8801d1095f00 task.stack:

Re: [RFC PATCH] blk-mq: fixup RESTART when queue becomes idle

On 1/19/18 9:37 AM, Ming Lei wrote: > On Fri, Jan 19, 2018 at 09:27:46AM -0700, Jens Axboe wrote: >> On 1/19/18 9:26 AM, Ming Lei wrote: >>> On Fri, Jan 19, 2018 at 09:19:24AM -0700, Jens Axboe wrote: On 1/19/18 9:05 AM, Ming Lei wrote: > On Fri, Jan 19, 2018 at 08:48:55AM -0700, Jens

Re: [RFC PATCH] blk-mq: fixup RESTART when queue becomes idle

On 1/19/18 9:37 AM, Ming Lei wrote: > On Fri, Jan 19, 2018 at 09:27:46AM -0700, Jens Axboe wrote: >> On 1/19/18 9:26 AM, Ming Lei wrote: >>> On Fri, Jan 19, 2018 at 09:19:24AM -0700, Jens Axboe wrote: On 1/19/18 9:05 AM, Ming Lei wrote: > On Fri, Jan 19, 2018 at 08:48:55AM -0700, Jens

Re: [PATCH] general protection fault in sock_has_perm

On 1/19/2018 9:06 AM, Paul Moore wrote: > On Fri, Jan 19, 2018 at 10:49 AM, Mark Salyzyn wrote: >> On 01/18/2018 02:36 PM, Paul Moore wrote: >>> On Thu, Jan 18, 2018 at 4:58 PM, Mark Salyzyn wrote: general protection fault: [#1] PREEMPT SMP

Re: [PATCH] general protection fault in sock_has_perm

On 1/19/2018 9:06 AM, Paul Moore wrote: > On Fri, Jan 19, 2018 at 10:49 AM, Mark Salyzyn wrote: >> On 01/18/2018 02:36 PM, Paul Moore wrote: >>> On Thu, Jan 18, 2018 at 4:58 PM, Mark Salyzyn wrote: general protection fault: [#1] PREEMPT SMP KASAN CPU: 1 PID: 14233 Comm:

Re: [PATCH] string: drop __must_check from strscpy() and restore strscpy() usages in cgroup

On Fri, Jan 19, 2018 at 9:31 AM, Tejun Heo wrote: > > I see. I'll push it your way together with other cgroup changes once > the merge window opens. NP. This was a fairly unusual late rc window. It's normally quiet this period, but first I was distracted by some of the Spectre

Re: [PATCH] string: drop __must_check from strscpy() and restore strscpy() usages in cgroup

On Fri, Jan 19, 2018 at 9:31 AM, Tejun Heo wrote: > > I see. I'll push it your way together with other cgroup changes once > the merge window opens. NP. This was a fairly unusual late rc window. It's normally quiet this period, but first I was distracted by some of the Spectre detail

Re: [PATCH] general protection fault in sock_has_perm

On 01/19/2018 09:19 AM, Stephen Smalley wrote: On Thu, 2018-01-18 at 13:58 -0800, Mark Salyzyn wrote: general protection fault: [#1] PREEMPT SMP KASAN . . . diff --git a/security/selinux/hooks.c b/security/selinux/hooks.c index 8644d864e3c1..95d7c8143373 100644 ---

Re: [PATCH] general protection fault in sock_has_perm

On 01/19/2018 09:19 AM, Stephen Smalley wrote: On Thu, 2018-01-18 at 13:58 -0800, Mark Salyzyn wrote: general protection fault: [#1] PREEMPT SMP KASAN . . . diff --git a/security/selinux/hooks.c b/security/selinux/hooks.c index 8644d864e3c1..95d7c8143373 100644 ---

Re: [PATCH V5 4/8] perf/x86/intel/uncore: add new data structures for free running counters

On Fri, Jan 19, 2018 at 9:19 AM, Peter Zijlstra wrote: > > On Fri, Jan 19, 2018 at 03:15:00PM +, Liang, Kan wrote: > > > > > > On Thu, Jan 18, 2018 at 05:43:10PM +, Liang, Kan wrote: > > > > In the uncore document, there is no event-code assigned to free running > >

Re: [PATCH V5 4/8] perf/x86/intel/uncore: add new data structures for free running counters

On Fri, Jan 19, 2018 at 9:19 AM, Peter Zijlstra wrote: > > On Fri, Jan 19, 2018 at 03:15:00PM +, Liang, Kan wrote: > > > > > > On Thu, Jan 18, 2018 at 05:43:10PM +, Liang, Kan wrote: > > > > In the uncore document, there is no event-code assigned to free running > > > counters. > > > >

Re: [RESEND PATCH] Documentation: input: ff: fix small typos

On Thu, Jan 18, 2018 at 04:49:03PM -0500, Jean-François Têtu wrote: > Fix small typos in the Instructions and Uploading sections. Fix a typo in > the start/stop effect example usage code. > > Signed-off-by: Jean-François Têtu Applied, thank you. > --- >

Re: [RESEND PATCH] Documentation: input: ff: fix small typos

On Thu, Jan 18, 2018 at 04:49:03PM -0500, Jean-François Têtu wrote: > Fix small typos in the Instructions and Uploading sections. Fix a typo in > the start/stop effect example usage code. > > Signed-off-by: Jean-François Têtu Applied, thank you. > --- > Documentation/input/ff.rst | 6 +++--- >

Re: [PATCH] input: touchscreen: remove atmel-wm97xx

On Fri, Jan 19, 2018 at 11:50:58AM +0100, Hans-Christian Noren Egtvedt wrote: > Around Fri 19 Jan 2018 09:17:45 +0100 or thereabout, Corentin Labbe wrote: > > Since AVR32 arch is gone, atmel-wm97xx driver is useless. > > Remove it. > > In theory it could have been rewritten to work with AT91

Re: [PATCH] input: touchscreen: remove atmel-wm97xx

On Fri, Jan 19, 2018 at 11:50:58AM +0100, Hans-Christian Noren Egtvedt wrote: > Around Fri 19 Jan 2018 09:17:45 +0100 or thereabout, Corentin Labbe wrote: > > Since AVR32 arch is gone, atmel-wm97xx driver is useless. > > Remove it. > > In theory it could have been rewritten to work with AT91

Re: [PATCH] string: drop __must_check from strscpy() and restore strscpy() usages in cgroup

Hello, On Fri, Jan 19, 2018 at 09:27:50AM -0800, Linus Torvalds wrote: > On Fri, Jan 19, 2018 at 8:50 AM, Tejun Heo wrote: > > > > Applied to cgroup/for-4.16. > > I did still have it queued up, but I was looking at other issues, and > hadn't gotten around to it. But if it's now

Re: [PATCH] string: drop __must_check from strscpy() and restore strscpy() usages in cgroup

Hello, On Fri, Jan 19, 2018 at 09:27:50AM -0800, Linus Torvalds wrote: > On Fri, Jan 19, 2018 at 8:50 AM, Tejun Heo wrote: > > > > Applied to cgroup/for-4.16. > > I did still have it queued up, but I was looking at other issues, and > hadn't gotten around to it. But if it's now in your git tree

[PATCH] NTB: ntb_perf: fix cast to restricted __le32

Sparse is whining about the u32 and __le32 mixed usage in the driver. drivers/ntb/test/ntb_perf.c:288:21: warning: cast to restricted __le32 drivers/ntb/test/ntb_perf.c:295:37: warning: incorrect type in argument 4 (different base types) drivers/ntb/test/ntb_perf.c:295:37:expected unsigned

[PATCH] NTB: ntb_perf: fix cast to restricted __le32

Sparse is whining about the u32 and __le32 mixed usage in the driver. drivers/ntb/test/ntb_perf.c:288:21: warning: cast to restricted __le32 drivers/ntb/test/ntb_perf.c:295:37: warning: incorrect type in argument 4 (different base types) drivers/ntb/test/ntb_perf.c:295:37:expected unsigned

Re: [PATCH] Support tablet mode switch for Dell laptops

On Fri, Jan 19, 2018 at 04:09:09PM +, mario.limoncie...@dell.com wrote: > > -Original Message- > > From: platform-driver-x86-ow...@vger.kernel.org [mailto:platform-driver-x86- > > ow...@vger.kernel.org] On Behalf Of Pali Rohár > > Sent: Friday, January 19, 2018 10:01 AM > > To: Dmitry

Re: [PATCH] Support tablet mode switch for Dell laptops

On Fri, Jan 19, 2018 at 04:09:09PM +, mario.limoncie...@dell.com wrote: > > -Original Message- > > From: platform-driver-x86-ow...@vger.kernel.org [mailto:platform-driver-x86- > > ow...@vger.kernel.org] On Behalf Of Pali Rohár > > Sent: Friday, January 19, 2018 10:01 AM > > To: Dmitry

Re: [PATCH v2 01/10] perf tools: Integrating the CoreSight decoding library

On 19 January 2018 at 08:55, Arnaldo Carvalho de Melo wrote: > Em Fri, Jan 19, 2018 at 08:24:56AM -0700, Mathieu Poirier escreveu: >> On 19 January 2018 at 08:12, Jiri Olsa wrote: >> > On Fri, Jan 19, 2018 at 11:58:19AM -0300, Arnaldo Carvalho de Melo wrote: >>

Re: [PATCH v2 01/10] perf tools: Integrating the CoreSight decoding library

On 19 January 2018 at 08:55, Arnaldo Carvalho de Melo wrote: > Em Fri, Jan 19, 2018 at 08:24:56AM -0700, Mathieu Poirier escreveu: >> On 19 January 2018 at 08:12, Jiri Olsa wrote: >> > On Fri, Jan 19, 2018 at 11:58:19AM -0300, Arnaldo Carvalho de Melo wrote: >> >> Em Thu, Jan 18, 2018 at

Re: [PATCH] string: drop __must_check from strscpy() and restore strscpy() usages in cgroup

On Fri, Jan 19, 2018 at 8:50 AM, Tejun Heo wrote: > > Applied to cgroup/for-4.16. I did still have it queued up, but I was looking at other issues, and hadn't gotten around to it. But if it's now in your git tree I can just drop this from my queue. Just as well. Thanks,

Re: [PATCH] string: drop __must_check from strscpy() and restore strscpy() usages in cgroup

On Fri, Jan 19, 2018 at 8:50 AM, Tejun Heo wrote: > > Applied to cgroup/for-4.16. I did still have it queued up, but I was looking at other issues, and hadn't gotten around to it. But if it's now in your git tree I can just drop this from my queue. Just as well. Thanks, Linus

I am waiting to hear from you soon,

From The international Investigation Financial Crime Unit Dear sir We need your urgent information sir I am writing to inform you that we are the international investigation financial crime unit and We have discovered through our network E-mail system This Week that your Inheritance Claim

I am waiting to hear from you soon,

From The international Investigation Financial Crime Unit Dear sir We need your urgent information sir I am writing to inform you that we are the international investigation financial crime unit and We have discovered through our network E-mail system This Week that your Inheritance Claim

Re: [RFC PATCH] blk-mq: fixup RESTART when queue becomes idle

On Fri, Jan 19, 2018 at 10:09:11AM -0700, Jens Axboe wrote: > On 1/19/18 10:05 AM, Ming Lei wrote: > > On Fri, Jan 19, 2018 at 09:52:32AM -0700, Jens Axboe wrote: > >> On 1/19/18 9:47 AM, Mike Snitzer wrote: > >>> On Fri, Jan 19 2018 at 11:41am -0500, > >>> Jens Axboe wrote: >

Re: [RFC PATCH] blk-mq: fixup RESTART when queue becomes idle

On Fri, Jan 19, 2018 at 10:09:11AM -0700, Jens Axboe wrote: > On 1/19/18 10:05 AM, Ming Lei wrote: > > On Fri, Jan 19, 2018 at 09:52:32AM -0700, Jens Axboe wrote: > >> On 1/19/18 9:47 AM, Mike Snitzer wrote: > >>> On Fri, Jan 19 2018 at 11:41am -0500, > >>> Jens Axboe wrote: > >>> > On

Re: Failing S3 resume since "Add missing irqflags tracing to native_load_gs_index()"

On 2018-01-06 09:55 AM, Harry Wentland wrote: > On 2018-01-05 06:07 PM, Andy Lutomirski wrote: >> >> >>> On Jan 5, 2018, at 1:51 PM, Harry Wentland wrote: >>> On 2018-01-05 04:28 PM, Andy Lutomirski wrote: It's a known issue, and it should be fixed in newer -rc

Re: Failing S3 resume since "Add missing irqflags tracing to native_load_gs_index()"

On 2018-01-06 09:55 AM, Harry Wentland wrote: > On 2018-01-05 06:07 PM, Andy Lutomirski wrote: >> >> >>> On Jan 5, 2018, at 1:51 PM, Harry Wentland wrote: >>> On 2018-01-05 04:28 PM, Andy Lutomirski wrote: It's a known issue, and it should be fixed in newer -rc kernels. >>> >>> I'm

Re: [PATCH V5 4/8] perf/x86/intel/uncore: add new data structures for free running counters

On Fri, Jan 19, 2018 at 03:15:00PM +, Liang, Kan wrote: > > > > On Thu, Jan 18, 2018 at 05:43:10PM +, Liang, Kan wrote: > > > In the uncore document, there is no event-code assigned to free running > > counters. > > > Some events need to be defined to indicate the free running counters. >

Re: [PATCH V5 4/8] perf/x86/intel/uncore: add new data structures for free running counters

On Fri, Jan 19, 2018 at 03:15:00PM +, Liang, Kan wrote: > > > > On Thu, Jan 18, 2018 at 05:43:10PM +, Liang, Kan wrote: > > > In the uncore document, there is no event-code assigned to free running > > counters. > > > Some events need to be defined to indicate the free running counters. >

Re: kernel BUG at net/core/skbuff.c:LINE! (2)

On Tue, Jan 16, 2018 at 04:21:40PM +0800, Xin Long wrote: > ipv4 tunnels don't really set dev->hard_header_len properly, > we may should fix it in pppoe by using needed_headroom, > as what it doesn't in arp_create. > I'm a bit in doubt about which device needs to be fixed. Should ip_gre set

Re: kernel BUG at net/core/skbuff.c:LINE! (2)

On Tue, Jan 16, 2018 at 04:21:40PM +0800, Xin Long wrote: > ipv4 tunnels don't really set dev->hard_header_len properly, > we may should fix it in pppoe by using needed_headroom, > as what it doesn't in arp_create. > I'm a bit in doubt about which device needs to be fixed. Should ip_gre set

Re: [PATCH] ARM: pxa/tosa-bt: add MODULE_LICENSE tag

Arnd Bergmann writes: > On Wed, Jan 10, 2018 at 9:22 PM, Robert Jarzmik > wrote: >> Arnd Bergmann writes: >> >>> Without this tag, we get a build warning: >>> >>> WARNING: modpost: missing MODULE_LICENSE() in arch/arm/mach-pxa/tosa-bt.o

Re: [PATCH] ARM: pxa/tosa-bt: add MODULE_LICENSE tag

Arnd Bergmann writes: > On Wed, Jan 10, 2018 at 9:22 PM, Robert Jarzmik > wrote: >> Arnd Bergmann writes: >> >>> Without this tag, we get a build warning: >>> >>> WARNING: modpost: missing MODULE_LICENSE() in arch/arm/mach-pxa/tosa-bt.o >>> >>> For completeness, I'm also adding author and

Re: [PATCH] general protection fault in sock_has_perm

On Thu, 2018-01-18 at 13:58 -0800, Mark Salyzyn wrote: > general protection fault: [#1] PREEMPT SMP KASAN > CPU: 1 PID: 14233 Comm: syz-executor2 Not tainted 4.4.112-g5f6325b > #28 > task: 8801d1095f00 task.stack: 8800b595 > RIP: 0010:[] [] > sock_has_perm+0x1fe/0x3e0

Re: [PATCH] general protection fault in sock_has_perm

On Thu, 2018-01-18 at 13:58 -0800, Mark Salyzyn wrote: > general protection fault: [#1] PREEMPT SMP KASAN > CPU: 1 PID: 14233 Comm: syz-executor2 Not tainted 4.4.112-g5f6325b > #28 > task: 8801d1095f00 task.stack: 8800b595 > RIP: 0010:[] [] > sock_has_perm+0x1fe/0x3e0

Re: [PATCH driver-core] kernfs: fix regression in kernfs_fop_write caused by wrong type

On Fri, Jan 19, 2018 at 09:16:36AM -0800, Tejun Heo wrote: > On Fri, Jan 19, 2018 at 09:18:54AM +0100, Ivan Vecera wrote: > > Commit b7ce40cff0b9 ("kernfs: cache atomic_write_len in > > kernfs_open_file") changes type of local variable 'len' from ssize_t > > to size_t. This change caused that the

Re: [PATCH driver-core] kernfs: fix regression in kernfs_fop_write caused by wrong type

On Fri, Jan 19, 2018 at 09:16:36AM -0800, Tejun Heo wrote: > On Fri, Jan 19, 2018 at 09:18:54AM +0100, Ivan Vecera wrote: > > Commit b7ce40cff0b9 ("kernfs: cache atomic_write_len in > > kernfs_open_file") changes type of local variable 'len' from ssize_t > > to size_t. This change caused that the

Re: [PATCH driver-core] kernfs: fix regression in kernfs_fop_write caused by wrong type

On Fri, Jan 19, 2018 at 09:18:54AM +0100, Ivan Vecera wrote: > Commit b7ce40cff0b9 ("kernfs: cache atomic_write_len in > kernfs_open_file") changes type of local variable 'len' from ssize_t > to size_t. This change caused that the *ppos value is updated also > when the previous write callback

Re: [PATCH driver-core] kernfs: fix regression in kernfs_fop_write caused by wrong type

On Fri, Jan 19, 2018 at 09:18:54AM +0100, Ivan Vecera wrote: > Commit b7ce40cff0b9 ("kernfs: cache atomic_write_len in > kernfs_open_file") changes type of local variable 'len' from ssize_t > to size_t. This change caused that the *ppos value is updated also > when the previous write callback

[GIT PULL] libata fixes for v4.15-rc8

Hello, Linus. This just adds one more entry for liteon optical drives to the device blacklist for large IOs. The change is very low risk. Thanks. The following changes since commit 2dc0b46b5ea30f169b0b272253ea846a5a281731: libata: sata_down_spd_limit should return if driver has not recorded

[GIT PULL] libata fixes for v4.15-rc8

Hello, Linus. This just adds one more entry for liteon optical drives to the device blacklist for large IOs. The change is very low risk. Thanks. The following changes since commit 2dc0b46b5ea30f169b0b272253ea846a5a281731: libata: sata_down_spd_limit should return if driver has not recorded

Re: [PATCH v3 0/5] x86: SME: BSP/SME microcode update fix

On 1/19/2018 10:02 AM, Gabriel C wrote: > 2018-01-19 16:56 GMT+01:00 Tom Lendacky : >> On 1/19/2018 9:35 AM, Greg Kroah-Hartman wrote: >>> On Fri, Jan 19, 2018 at 09:27:47AM -0600, Tom Lendacky wrote: On 1/19/2018 9:11 AM, Greg Kroah-Hartman wrote: > On Fri, Jan

Re: [PATCH v3 0/5] x86: SME: BSP/SME microcode update fix

On 1/19/2018 10:02 AM, Gabriel C wrote: > 2018-01-19 16:56 GMT+01:00 Tom Lendacky : >> On 1/19/2018 9:35 AM, Greg Kroah-Hartman wrote: >>> On Fri, Jan 19, 2018 at 09:27:47AM -0600, Tom Lendacky wrote: On 1/19/2018 9:11 AM, Greg Kroah-Hartman wrote: > On Fri, Jan 19, 2018 at 09:03:52AM

Re: net: r8169: a question of memory barrier in the r8169 driver

On Fri, Jan 19, 2018 at 02:11:18AM +0100, Francois Romieu wrote: > Peter Zijlstra : > [...] > > There is only 1 variable afaict. Memory barriers need at least 2 in > > order to be able to do _anything_. > > I don't get your point: why don't {cur_tx, dirty_tx} qualify as

Re: net: r8169: a question of memory barrier in the r8169 driver

On Fri, Jan 19, 2018 at 02:11:18AM +0100, Francois Romieu wrote: > Peter Zijlstra : > [...] > > There is only 1 variable afaict. Memory barriers need at least 2 in > > order to be able to do _anything_. > > I don't get your point: why don't {cur_tx, dirty_tx} qualify as said > two variables ?

Re: [PATCH] media: v4l: omap_vout: vrfb: Use the wrapper for prep_interleaved_dma()

Hi, Peter! :-) How do you do? On Fri, Jan 19, 2018 at 03:34:34PM +0200, Peter Ujfalusi wrote: > Instead of directly accessing to dmadev->device_prep_interleaved_dma() use > the dmaengine_prep_interleaved_dma() wrapper instead. > > Signed-off-by: Peter Ujfalusi Acked-by:

Re: [PATCH] media: v4l: omap_vout: vrfb: Use the wrapper for prep_interleaved_dma()

Hi, Peter! :-) How do you do? On Fri, Jan 19, 2018 at 03:34:34PM +0200, Peter Ujfalusi wrote: > Instead of directly accessing to dmadev->device_prep_interleaved_dma() use > the dmaengine_prep_interleaved_dma() wrapper instead. > > Signed-off-by: Peter Ujfalusi Acked-by: Sakari Ailus --

Re: [Intel-gfx] [RFC] perf: Allow fine-grained PMU access control

Hi, On 19/01/2018 16:45, Peter Zijlstra wrote: On Thu, Jan 18, 2018 at 06:40:07PM +, Tvrtko Ursulin wrote: From: Tvrtko Ursulin For situations where sysadmins might want to allow different level of of access control for different PMUs, we start creating per-PMU

Re: [Intel-gfx] [RFC] perf: Allow fine-grained PMU access control

Hi, On 19/01/2018 16:45, Peter Zijlstra wrote: On Thu, Jan 18, 2018 at 06:40:07PM +, Tvrtko Ursulin wrote: From: Tvrtko Ursulin For situations where sysadmins might want to allow different level of of access control for different PMUs, we start creating per-PMU perf_event_paranoid

Re: [RFC PATCH] blk-mq: fixup RESTART when queue becomes idle

On 1/19/18 10:05 AM, Ming Lei wrote: > On Fri, Jan 19, 2018 at 09:52:32AM -0700, Jens Axboe wrote: >> On 1/19/18 9:47 AM, Mike Snitzer wrote: >>> On Fri, Jan 19 2018 at 11:41am -0500, >>> Jens Axboe wrote: >>> On 1/19/18 9:37 AM, Ming Lei wrote: > On Fri, Jan 19, 2018 at

Re: [RFC PATCH] blk-mq: fixup RESTART when queue becomes idle

On 1/19/18 10:05 AM, Ming Lei wrote: > On Fri, Jan 19, 2018 at 09:52:32AM -0700, Jens Axboe wrote: >> On 1/19/18 9:47 AM, Mike Snitzer wrote: >>> On Fri, Jan 19 2018 at 11:41am -0500, >>> Jens Axboe wrote: >>> On 1/19/18 9:37 AM, Ming Lei wrote: > On Fri, Jan 19, 2018 at 09:27:46AM

Re: [PATCH] general protection fault in sock_has_perm

On Fri, Jan 19, 2018 at 10:49 AM, Mark Salyzyn wrote: > On 01/18/2018 02:36 PM, Paul Moore wrote: >> On Thu, Jan 18, 2018 at 4:58 PM, Mark Salyzyn wrote: >>> general protection fault: [#1] PREEMPT SMP KASAN >>> CPU: 1 PID: 14233 Comm: syz-executor2

Re: [PATCH] general protection fault in sock_has_perm

On Fri, Jan 19, 2018 at 10:49 AM, Mark Salyzyn wrote: > On 01/18/2018 02:36 PM, Paul Moore wrote: >> On Thu, Jan 18, 2018 at 4:58 PM, Mark Salyzyn wrote: >>> general protection fault: [#1] PREEMPT SMP KASAN >>> CPU: 1 PID: 14233 Comm: syz-executor2 Not tainted 4.4.112-g5f6325b #28 >>> . . .

Re: [RFC PATCH] blk-mq: fixup RESTART when queue becomes idle

On Fri, Jan 19, 2018 at 09:52:32AM -0700, Jens Axboe wrote: > On 1/19/18 9:47 AM, Mike Snitzer wrote: > > On Fri, Jan 19 2018 at 11:41am -0500, > > Jens Axboe wrote: > > > >> On 1/19/18 9:37 AM, Ming Lei wrote: > >>> On Fri, Jan 19, 2018 at 09:27:46AM -0700, Jens Axboe wrote: >

Re: [RFC PATCH] blk-mq: fixup RESTART when queue becomes idle

On Fri, Jan 19, 2018 at 09:52:32AM -0700, Jens Axboe wrote: > On 1/19/18 9:47 AM, Mike Snitzer wrote: > > On Fri, Jan 19 2018 at 11:41am -0500, > > Jens Axboe wrote: > > > >> On 1/19/18 9:37 AM, Ming Lei wrote: > >>> On Fri, Jan 19, 2018 at 09:27:46AM -0700, Jens Axboe wrote: > On 1/19/18

Re: [PATCH v10 27/27] mm: display pkey in smaps if arch_pkeys_enabled() is true

Ram Pai writes: > On Fri, Jan 19, 2018 at 10:09:41AM -0600, Eric W. Biederman wrote: >> Ram Pai writes: >> >> > Currently the architecture specific code is expected to >> > display the protection keys in smap for a given vma. >> > This can lead

Re: [PATCH v10 27/27] mm: display pkey in smaps if arch_pkeys_enabled() is true

Ram Pai writes: > On Fri, Jan 19, 2018 at 10:09:41AM -0600, Eric W. Biederman wrote: >> Ram Pai writes: >> >> > Currently the architecture specific code is expected to >> > display the protection keys in smap for a given vma. >> > This can lead to redundant code and possibly to

[GIT PULL] ARM: SoC fixes for 4.15

The following changes since commit b2cd1df66037e7c4697c7e40496bf7e4a5e16a2d: Linux 4.15-rc7 (2018-01-07 14:22:41 -0800) are available in the git repository at: git://git.kernel.org/pub/scm/linux/kernel/git/arm/arm-soc.git tags/armsoc-fixes for you to fetch changes up to

[GIT PULL] ARM: SoC fixes for 4.15

The following changes since commit b2cd1df66037e7c4697c7e40496bf7e4a5e16a2d: Linux 4.15-rc7 (2018-01-07 14:22:41 -0800) are available in the git repository at: git://git.kernel.org/pub/scm/linux/kernel/git/arm/arm-soc.git tags/armsoc-fixes for you to fetch changes up to

Re: [PATCH 1/3] soc-knav_dma: Use seq_putc() in dma_debug_show_channels()

On 5/1/2017 12:27 PM, SF Markus Elfring wrote: From: Markus Elfring Date: Mon, 1 May 2017 20:55:55 +0200 A single character (line break) should be put into a sequence. Thus use the corresponding function "seq_putc". This issue was detected by using the

Re: [PATCH 1/3] soc-knav_dma: Use seq_putc() in dma_debug_show_channels()

On 5/1/2017 12:27 PM, SF Markus Elfring wrote: From: Markus Elfring Date: Mon, 1 May 2017 20:55:55 +0200 A single character (line break) should be put into a sequence. Thus use the corresponding function "seq_putc". This issue was detected by using the Coccinelle software. Signed-off-by:

[GIT PULL] workqueue fixes for v4.15-rc8

Hello, Linus. One patch to add touch_nmi_watchdog() while dumping workqueue debug messages to avoid triggering the lockup detector spuriously. The change is very low risk. Thanks. The following changes since commit 01dfee9582d9b4403c4902df096ed8b43d55181c: workqueue: remove unneeded

[GIT PULL] workqueue fixes for v4.15-rc8

Hello, Linus. One patch to add touch_nmi_watchdog() while dumping workqueue debug messages to avoid triggering the lockup detector spuriously. The change is very low risk. Thanks. The following changes since commit 01dfee9582d9b4403c4902df096ed8b43d55181c: workqueue: remove unneeded

Re: [RFC PATCH v2] ima,fuse: introduce new fs flag FS_NO_IMA_CACHE

On Fri, 2018-01-19 at 11:35 +0100, Alban Crequy wrote: > On Thu, Jan 18, 2018 at 10:25 PM, Mimi Zohar wrote: > > On Tue, 2018-01-16 at 16:10 +0100, Alban Crequy wrote: > >> From: Alban Crequy > >> > >> This patch forces files to be re-measured,

Re: [RFC PATCH v2] ima,fuse: introduce new fs flag FS_NO_IMA_CACHE

On Fri, 2018-01-19 at 11:35 +0100, Alban Crequy wrote: > On Thu, Jan 18, 2018 at 10:25 PM, Mimi Zohar wrote: > > On Tue, 2018-01-16 at 16:10 +0100, Alban Crequy wrote: > >> From: Alban Crequy > >> > >> This patch forces files to be re-measured, re-appraised and re-audited > >> on file systems

Re: [RFC] Per file OOM badness

Am 19.01.2018 um 13:20 schrieb Michal Hocko: On Fri 19-01-18 13:13:51, Michal Hocko wrote: On Fri 19-01-18 12:37:51, Christian König wrote: [...] The per file descriptor badness is/was just the much easier approach to solve the issue, because the drivers already knew which client is currently

Re: [RFC] Per file OOM badness

Am 19.01.2018 um 13:20 schrieb Michal Hocko: On Fri 19-01-18 13:13:51, Michal Hocko wrote: On Fri 19-01-18 12:37:51, Christian König wrote: [...] The per file descriptor badness is/was just the much easier approach to solve the issue, because the drivers already knew which client is currently

Re: [RFC PATCH] blk-mq: fixup RESTART when queue becomes idle

On 1/19/18 9:47 AM, Mike Snitzer wrote: > On Fri, Jan 19 2018 at 11:41am -0500, > Jens Axboe wrote: > >> On 1/19/18 9:37 AM, Ming Lei wrote: >>> On Fri, Jan 19, 2018 at 09:27:46AM -0700, Jens Axboe wrote: On 1/19/18 9:26 AM, Ming Lei wrote: > On Fri, Jan 19, 2018 at

Re: [RFC PATCH] blk-mq: fixup RESTART when queue becomes idle

On 1/19/18 9:47 AM, Mike Snitzer wrote: > On Fri, Jan 19 2018 at 11:41am -0500, > Jens Axboe wrote: > >> On 1/19/18 9:37 AM, Ming Lei wrote: >>> On Fri, Jan 19, 2018 at 09:27:46AM -0700, Jens Axboe wrote: On 1/19/18 9:26 AM, Ming Lei wrote: > On Fri, Jan 19, 2018 at 09:19:24AM -0700,

Re: [PATCH v10 27/27] mm: display pkey in smaps if arch_pkeys_enabled() is true

On Fri, Jan 19, 2018 at 10:09:41AM -0600, Eric W. Biederman wrote: > Ram Pai writes: > > > Currently the architecture specific code is expected to > > display the protection keys in smap for a given vma. > > This can lead to redundant code and possibly to divergent >

Re: [PATCH v10 27/27] mm: display pkey in smaps if arch_pkeys_enabled() is true

On Fri, Jan 19, 2018 at 10:09:41AM -0600, Eric W. Biederman wrote: > Ram Pai writes: > > > Currently the architecture specific code is expected to > > display the protection keys in smap for a given vma. > > This can lead to redundant code and possibly to divergent > > formats in which

Re: [PATCH] string: drop __must_check from strscpy() and restore strscpy() usages in cgroup

On Tue, Jan 09, 2018 at 07:21:15AM -0800, Tejun Heo wrote: > From ceb2d2b2e496f180be95adb670337bb254f89323 Mon Sep 17 00:00:00 2001 > From: Tejun Heo > Date: Tue, 9 Jan 2018 07:00:29 -0800 > MIME-Version: 1.0 > Content-Type: text/plain; charset=UTF-8 > Content-Transfer-Encoding:

Re: [PATCH] string: drop __must_check from strscpy() and restore strscpy() usages in cgroup

On Tue, Jan 09, 2018 at 07:21:15AM -0800, Tejun Heo wrote: > From ceb2d2b2e496f180be95adb670337bb254f89323 Mon Sep 17 00:00:00 2001 > From: Tejun Heo > Date: Tue, 9 Jan 2018 07:00:29 -0800 > MIME-Version: 1.0 > Content-Type: text/plain; charset=UTF-8 > Content-Transfer-Encoding: 8bit Applied to

Re: [RFC] Per file OOM badness

On 2018-01-19 12:37 PM, Christian König wrote: > Am 19.01.2018 um 11:40 schrieb Michal Hocko: >> On Fri 19-01-18 09:39:03, Christian König wrote: >>> Am 19.01.2018 um 09:20 schrieb Michal Hocko: >> [...] OK, in that case I would propose a different approach. We already have rss_stat. So

Re: [RFC] Per file OOM badness

On 2018-01-19 12:37 PM, Christian König wrote: > Am 19.01.2018 um 11:40 schrieb Michal Hocko: >> On Fri 19-01-18 09:39:03, Christian König wrote: >>> Am 19.01.2018 um 09:20 schrieb Michal Hocko: >> [...] OK, in that case I would propose a different approach. We already have rss_stat. So

Re: [PATCH 34/35] x86/kvm: Add IBPB support

On 19/01/2018 17:08, David Woodhouse wrote: > On Fri, 2018-01-19 at 16:25 +0100, Paolo Bonzini wrote: >> Without retpolines, KVM userspace is not protected from the guest >> poisoning the BTB, because there is no IBRS-barrier on the vmexit >> path. >> So there are two more IBPBs that are needed if

Re: [PATCH 34/35] x86/kvm: Add IBPB support

On 19/01/2018 17:08, David Woodhouse wrote: > On Fri, 2018-01-19 at 16:25 +0100, Paolo Bonzini wrote: >> Without retpolines, KVM userspace is not protected from the guest >> poisoning the BTB, because there is no IBRS-barrier on the vmexit >> path. >> So there are two more IBPBs that are needed if

Re: [RFC PATCH] blk-mq: fixup RESTART when queue becomes idle

On Fri, Jan 19 2018 at 11:41am -0500, Jens Axboe wrote: > On 1/19/18 9:37 AM, Ming Lei wrote: > > On Fri, Jan 19, 2018 at 09:27:46AM -0700, Jens Axboe wrote: > >> On 1/19/18 9:26 AM, Ming Lei wrote: > >>> On Fri, Jan 19, 2018 at 09:19:24AM -0700, Jens Axboe wrote: > >> > >>

Re: [RFC PATCH] blk-mq: fixup RESTART when queue becomes idle

On Fri, Jan 19 2018 at 11:41am -0500, Jens Axboe wrote: > On 1/19/18 9:37 AM, Ming Lei wrote: > > On Fri, Jan 19, 2018 at 09:27:46AM -0700, Jens Axboe wrote: > >> On 1/19/18 9:26 AM, Ming Lei wrote: > >>> On Fri, Jan 19, 2018 at 09:19:24AM -0700, Jens Axboe wrote: > >> > >> There are no pending

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