Re: perf: bisected sampling bug in Linux 4.11-rc1
On Tue, 18 Jul 2017, Ingo Molnar wrote: > > Ok, great - if this works then I'll pick up this fix instead of the revert > that > I've queued up earlier today. sorry for the delay, I was out of town for a few days. I've tried the patch and it looks like it fixes the test in question and doesn't seem to add any other regressions. Vince
Re: perf: bisected sampling bug in Linux 4.11-rc1
* Alexander Shishkin wrote: > Vince Weaver writes: > > > I was tracking down some regressions in my perf_event_test testsuite. > > Some of the tests broke in the 4.11-rc1 timeframe. > > > > I've bisected one of them, this report is about > > tests/overflow/simul_oneshot_group_overflow > > This test creates an event group containing two sampling events, set > > to overflow to a signal handler (which disables and then refreshes the > > event). > > > > On a good kernel you get the following: > > Event perf::instructions with period 100 > > Event perf::instructions with period 200 > > fd 3 overflows: 946 (perf::instructions/100) > > fd 4 overflows: 473 (perf::instructions/200) > > Ending counts: > > Count 0: 946379875 > > Count 1: 946365218 > > > > With the broken kernels you get: > > Event perf::instructions with period 100 > > Event perf::instructions with period 200 > > fd 3 overflows: 938 (perf::instructions/100) > > fd 4 overflows: 318 (perf::instructions/200) > > Ending counts: > > Count 0: 946373080 > > Count 1: 653373058 > > > > > > 487f05e18aa4efacee6357480f293a5afe6593b5 is the first bad commit > > > > commit 487f05e18aa4efacee6357480f293a5afe6593b5 > > Author: Alexander Shishkin > > Date: Thu Jan 19 18:43:30 2017 +0200 > > Ok, there was a bug there indeed. This patch should take care of it and > should also be backportable in case it's stable-worthy. > > From 187d67c9908cb126656c34546772089c17a8e6c5 Mon Sep 17 00:00:00 2001 > From: Alexander Shishkin > Date: Tue, 18 Jul 2017 13:53:01 +0300 > Subject: [PATCH] perf: Fix scheduling regression of pinned groups Ok, great - if this works then I'll pick up this fix instead of the revert that I've queued up earlier today. Thanks, Ingo
Re: perf: bisected sampling bug in Linux 4.11-rc1
Vince Weaver writes:
> I was tracking down some regressions in my perf_event_test testsuite.
> Some of the tests broke in the 4.11-rc1 timeframe.
>
> I've bisected one of them, this report is about
> tests/overflow/simul_oneshot_group_overflow
> This test creates an event group containing two sampling events, set
> to overflow to a signal handler (which disables and then refreshes the
> event).
>
> On a good kernel you get the following:
> Event perf::instructions with period 100
> Event perf::instructions with period 200
> fd 3 overflows: 946 (perf::instructions/100)
> fd 4 overflows: 473 (perf::instructions/200)
> Ending counts:
> Count 0: 946379875
> Count 1: 946365218
>
> With the broken kernels you get:
> Event perf::instructions with period 100
> Event perf::instructions with period 200
> fd 3 overflows: 938 (perf::instructions/100)
> fd 4 overflows: 318 (perf::instructions/200)
> Ending counts:
> Count 0: 946373080
> Count 1: 653373058
>
>
> 487f05e18aa4efacee6357480f293a5afe6593b5 is the first bad commit
>
> commit 487f05e18aa4efacee6357480f293a5afe6593b5
> Author: Alexander Shishkin
> Date: Thu Jan 19 18:43:30 2017 +0200
Ok, there was a bug there indeed. This patch should take care of it and
should also be backportable in case it's stable-worthy.
>From 187d67c9908cb126656c34546772089c17a8e6c5 Mon Sep 17 00:00:00 2001
From: Alexander Shishkin
Date: Tue, 18 Jul 2017 13:53:01 +0300
Subject: [PATCH] perf: Fix scheduling regression of pinned groups
Commit 487f05e18a ("perf/core: Optimize event rescheduling on active
contexts") erronously assumed that event's 'pinned' setting determines
whether the event belongs to a pinned group or not, but in fact, it's
the group leader's pinned state that matters. This was discovered by
Vince in a test case where two instruction counters are grouped, the
group leader is pinned, but the other event is not; in the regressed
case the counters were off by 33% (the difference between events'
periods), but should be the same within the error margin.
This fixes the problem by looking at the group leader's pinning.
Reported-by: Vince Weaver
Signed-off-by: Alexander Shishkin
Fixes: 487f05e18a ("perf/core: Optimize event rescheduling on active contexts")
Cc: [email protected]
---
kernel/events/core.c | 7 +++
1 file changed, 7 insertions(+)
diff --git a/kernel/events/core.c b/kernel/events/core.c
index bc63f8db1b..1edbaf94dd 100644
--- a/kernel/events/core.c
+++ b/kernel/events/core.c
@@ -1451,6 +1451,13 @@ static enum event_type_t get_event_type(struct
perf_event *event)
lockdep_assert_held(&ctx->lock);
+ /*
+* It's 'group type', really, because if our group leader is
+* pinned, so are we.
+*/
+ if (event->group_leader != event)
+ event = event->group_leader;
+
event_type = event->attr.pinned ? EVENT_PINNED : EVENT_FLEXIBLE;
if (!ctx->task)
event_type |= EVENT_CPU;
--
2.11.0
Re: perf: bisected sampling bug in Linux 4.11-rc1
On Sat, 15 Jul 2017, Vince Weaver wrote: > Although there is a separate issue also introduced in 4.11-rc1 that still > fails a different testcase. I'm in the middle of bisecting that one and > probably won't have the result of the bisect until Monday. I went and bisected the other issue anyway. It wasn't in 4.11-rc1, but in 4.12-rc4. Yes, I have a test that triggered the c1582c231ea041 perf/core: Drop kernel samples even though :u is specified issue. The test was actually losing 7% of its samples, so not just a single sample here or there. The test had two events sampling, one at 100k and one at 200k so I guess every other sample would have two samples immediately back-to-back which must make it more likely to stray into the kernel. Vince
Re: perf: bisected sampling bug in Linux 4.11-rc1
On Sat, 15 Jul 2017, Ingo Molnar wrote: > > * Vince Weaver wrote: > > > 487f05e18aa4efacee6357480f293a5afe6593b5 is the first bad commit > > > > commit 487f05e18aa4efacee6357480f293a5afe6593b5 > > Author: Alexander Shishkin > > Date: Thu Jan 19 18:43:30 2017 +0200 > > > > perf/core: Optimize event rescheduling on active contexts > > BTW., just to prepare for the eventuality: below is a (completely > untested...) > revert of this commit, against recent kernels, with conflicts fixed up. > > Does this fix your testcase? Yes, applying this to current git fixes the testcase and doesn't seem to break anything else. Although there is a separate issue also introduced in 4.11-rc1 that still fails a different testcase. I'm in the middle of bisecting that one and probably won't have the result of the bisect until Monday. Vince
Re: perf: bisected sampling bug in Linux 4.11-rc1
* Vince Weaver wrote:
> 487f05e18aa4efacee6357480f293a5afe6593b5 is the first bad commit
>
> commit 487f05e18aa4efacee6357480f293a5afe6593b5
> Author: Alexander Shishkin
> Date: Thu Jan 19 18:43:30 2017 +0200
>
> perf/core: Optimize event rescheduling on active contexts
BTW., just to prepare for the eventuality: below is a (completely untested...)
revert of this commit, against recent kernels, with conflicts fixed up.
Does this fix your testcase?
Thanks,
Ingo
>From fe0deecf2a8e9f5097013bcf89a9ef4b80715be1 Mon Sep 17 00:00:00 2001
From: Ingo Molnar
Date: Sat, 15 Jul 2017 12:57:51 +0200
Subject: [PATCH] Revert "perf/core: Optimize event rescheduling on active
contexts"
This reverts commit 487f05e18aa4efacee6357480f293a5afe6593b5.
---
kernel/events/core.c | 80
1 file changed, 11 insertions(+), 69 deletions(-)
diff --git a/kernel/events/core.c b/kernel/events/core.c
index 9747e422ab20..778aa2548142 100644
--- a/kernel/events/core.c
+++ b/kernel/events/core.c
@@ -359,8 +359,6 @@ enum event_type_t {
EVENT_FLEXIBLE = 0x1,
EVENT_PINNED = 0x2,
EVENT_TIME = 0x4,
- /* see ctx_resched() for details */
- EVENT_CPU = 0x8,
EVENT_ALL = EVENT_FLEXIBLE | EVENT_PINNED,
};
@@ -1445,20 +1443,6 @@ static void update_group_times(struct perf_event *leader)
update_event_times(event);
}
-static enum event_type_t get_event_type(struct perf_event *event)
-{
- struct perf_event_context *ctx = event->ctx;
- enum event_type_t event_type;
-
- lockdep_assert_held(&ctx->lock);
-
- event_type = event->attr.pinned ? EVENT_PINNED : EVENT_FLEXIBLE;
- if (!ctx->task)
- event_type |= EVENT_CPU;
-
- return event_type;
-}
-
static struct list_head *
ctx_group_list(struct perf_event *event, struct perf_event_context *ctx)
{
@@ -2232,8 +2216,7 @@ ctx_sched_in(struct perf_event_context *ctx,
struct task_struct *task);
static void task_ctx_sched_out(struct perf_cpu_context *cpuctx,
- struct perf_event_context *ctx,
- enum event_type_t event_type)
+ struct perf_event_context *ctx)
{
if (!cpuctx->task_ctx)
return;
@@ -2241,7 +2224,7 @@ static void task_ctx_sched_out(struct perf_cpu_context
*cpuctx,
if (WARN_ON_ONCE(ctx != cpuctx->task_ctx))
return;
- ctx_sched_out(ctx, cpuctx, event_type);
+ ctx_sched_out(ctx, cpuctx, EVENT_ALL);
}
static void perf_event_sched_in(struct perf_cpu_context *cpuctx,
@@ -2256,51 +2239,13 @@ static void perf_event_sched_in(struct perf_cpu_context
*cpuctx,
ctx_sched_in(ctx, cpuctx, EVENT_FLEXIBLE, task);
}
-/*
- * We want to maintain the following priority of scheduling:
- * - CPU pinned (EVENT_CPU | EVENT_PINNED)
- * - task pinned (EVENT_PINNED)
- * - CPU flexible (EVENT_CPU | EVENT_FLEXIBLE)
- * - task flexible (EVENT_FLEXIBLE).
- *
- * In order to avoid unscheduling and scheduling back in everything every
- * time an event is added, only do it for the groups of equal priority and
- * below.
- *
- * This can be called after a batch operation on task events, in which case
- * event_type is a bit mask of the types of events involved. For CPU events,
- * event_type is only either EVENT_PINNED or EVENT_FLEXIBLE.
- */
static void ctx_resched(struct perf_cpu_context *cpuctx,
- struct perf_event_context *task_ctx,
- enum event_type_t event_type)
+ struct perf_event_context *task_ctx)
{
- enum event_type_t ctx_event_type = event_type & EVENT_ALL;
- bool cpu_event = !!(event_type & EVENT_CPU);
-
- /*
-* If pinned groups are involved, flexible groups also need to be
-* scheduled out.
-*/
- if (event_type & EVENT_PINNED)
- event_type |= EVENT_FLEXIBLE;
-
perf_pmu_disable(cpuctx->ctx.pmu);
if (task_ctx)
- task_ctx_sched_out(cpuctx, task_ctx, event_type);
-
- /*
-* Decide which cpu ctx groups to schedule out based on the types
-* of events that caused rescheduling:
-* - EVENT_CPU: schedule out corresponding groups;
-* - EVENT_PINNED task events: schedule out EVENT_FLEXIBLE groups;
-* - otherwise, do nothing more.
-*/
- if (cpu_event)
- cpu_ctx_sched_out(cpuctx, ctx_event_type);
- else if (ctx_event_type & EVENT_PINNED)
- cpu_ctx_sched_out(cpuctx, EVENT_FLEXIBLE);
-
+ task_ctx_sched_out(cpuctx, task_ctx);
+ cpu_ctx_sched_out(cpuctx, EVENT_ALL);
perf_event_sched_in(cpuctx, task_ctx, current);
perf_pmu_enable(cpuctx->ctx.pmu);
}
@@ -2347,7 +2292,7 @@ static int __perf_install_in_context(void *info)
if (reprogram) {
ctx_sched_out(ctx, cp
Re: perf: bisected sampling bug in Linux 4.11-rc1
On Fri, 14 Jul 2017, Alexander Shishkin wrote: > Vince Weaver writes: > > > I was tracking down some regressions in my perf_event_test testsuite. > > Some of the tests broke in the 4.11-rc1 timeframe. > > > > I've bisected one of them, this report is about > > tests/overflow/simul_oneshot_group_overflow > > This test creates an event group containing two sampling events, set > > to overflow to a signal handler (which disables and then refreshes the > > event). > > > > On a good kernel you get the following: > > Event perf::instructions with period 100 > > Event perf::instructions with period 200 > > fd 3 overflows: 946 (perf::instructions/100) > > fd 4 overflows: 473 (perf::instructions/200) > > Ending counts: > > Count 0: 946379875 > > Count 1: 946365218 > > > > With the broken kernels you get: > > Event perf::instructions with period 100 > > Event perf::instructions with period 200 > > fd 3 overflows: 938 (perf::instructions/100) > > fd 4 overflows: 318 (perf::instructions/200) > > Ending counts: > > Count 0: 946373080 > > Count 1: 653373058 > > I'm not sure I'm seeing it (granted, it's a friday evening): is it the > difference in overflow counts? It's two things. It's created an grouped event, with the two events both perf::instructions. 1. The total count at the end should be the same for both (on the failing kernels it is not) 2. The overflow count for both events should be roughly total_events/sample_freq. (on the failing kernels it is not) > Also, are they cpu or task bound? The open looks like this: perf_event_open(&pe,0,-1,-1,0); On the failing case, the group leader is pinned. The source code for the test is here: https://github.com/deater/perf_event_tests/blob/master/tests/overflow/simul_oneshot_group_overflow.c Vince
Re: perf: bisected sampling bug in Linux 4.11-rc1
Vince Weaver writes: > I was tracking down some regressions in my perf_event_test testsuite. > Some of the tests broke in the 4.11-rc1 timeframe. > > I've bisected one of them, this report is about > tests/overflow/simul_oneshot_group_overflow > This test creates an event group containing two sampling events, set > to overflow to a signal handler (which disables and then refreshes the > event). > > On a good kernel you get the following: > Event perf::instructions with period 100 > Event perf::instructions with period 200 > fd 3 overflows: 946 (perf::instructions/100) > fd 4 overflows: 473 (perf::instructions/200) > Ending counts: > Count 0: 946379875 > Count 1: 946365218 > > With the broken kernels you get: > Event perf::instructions with period 100 > Event perf::instructions with period 200 > fd 3 overflows: 938 (perf::instructions/100) > fd 4 overflows: 318 (perf::instructions/200) > Ending counts: > Count 0: 946373080 > Count 1: 653373058 I'm not sure I'm seeing it (granted, it's a friday evening): is it the difference in overflow counts? Also, are they cpu or task bound? Regards, -- Alex
Re: perf: bisected sampling bug in Linux 4.11-rc1
On Fri, 14 Jul 2017, Vince Weaver wrote: > On a good kernel you get the following: > Event perf::instructions with period 100 > Event perf::instructions with period 200 > fd 3 overflows: 946 (perf::instructions/100) > fd 4 overflows: 473 (perf::instructions/200) > Ending counts: > Count 0: 946379875 > Count 1: 946365218 > > With the broken kernels you get: > Event perf::instructions with period 100 > Event perf::instructions with period 200 > fd 3 overflows: 938 (perf::instructions/100) > fd 4 overflows: 318 (perf::instructions/200) > Ending counts: > Count 0: 946373080 > Count 1: 653373058 additional relevant detail: in the failing case, the group leader of the event set has .pinned=1 If I change that to .pinned=0 then the test passes. Vince
perf: bisected sampling bug in Linux 4.11-rc1
I was tracking down some regressions in my perf_event_test testsuite. Some of the tests broke in the 4.11-rc1 timeframe. I've bisected one of them, this report is about tests/overflow/simul_oneshot_group_overflow This test creates an event group containing two sampling events, set to overflow to a signal handler (which disables and then refreshes the event). On a good kernel you get the following: Event perf::instructions with period 100 Event perf::instructions with period 200 fd 3 overflows: 946 (perf::instructions/100) fd 4 overflows: 473 (perf::instructions/200) Ending counts: Count 0: 946379875 Count 1: 946365218 With the broken kernels you get: Event perf::instructions with period 100 Event perf::instructions with period 200 fd 3 overflows: 938 (perf::instructions/100) fd 4 overflows: 318 (perf::instructions/200) Ending counts: Count 0: 946373080 Count 1: 653373058 487f05e18aa4efacee6357480f293a5afe6593b5 is the first bad commit commit 487f05e18aa4efacee6357480f293a5afe6593b5 Author: Alexander Shishkin Date: Thu Jan 19 18:43:30 2017 +0200 perf/core: Optimize event rescheduling on active contexts When new events are added to an active context, we go and reschedule all cpu groups and all task groups in order to preserve the priority (cpu pinned, task pinned, cpu flexible, task flexible), but in reality we only need to reschedule groups of the same priority as that of the events being added, and below. This patch changes the behavior so that only groups that need to be rescheduled are rescheduled. Reported-by: Adrian Hunter Signed-off-by: Alexander Shishkin Signed-off-by: Peter Zijlstra (Intel) Cc: Arnaldo Carvalho de Melo Cc: Arnaldo Carvalho de Melo Cc: Jiri Olsa Cc: Linus Torvalds Cc: Peter Zijlstra Cc: Stephane Eranian Cc: Thomas Gleixner Cc: Vince Weaver Cc: [email protected] Link: http://lkml.kernel.org/r/[email protected] Signed-off-by: Ingo Molnar
Re: Linux 4.11 - broken enlightenment window manager (fixed in 4.12)
On Fri, Jun 09, 2017 at 09:35:09AM +0200, Ralph Sennhauser wrote:
> Hi Greg,
>
> With 4.11 the enlightenment window mangers fails to start setuid
> children due to commit 64b875f7ac8a ("ptrace: Capture the ptracer's
> creds not PT_PTRACE_CAP").
>
> Commit c70d9d809fde ("ptrace: Properly initialize ptracer_cred on
> fork") in Linus tree fixes the issue. Tested with v4.11.4. Please
> consider cherry-picking.
Sorry for the delay, others also asked for this, I'll try to get to it
for the next release.
greg k-h
Linux 4.11 - broken enlightenment window manager (fixed in 4.12)
Hi Greg,
With 4.11 the enlightenment window mangers fails to start setuid
children due to commit 64b875f7ac8a ("ptrace: Capture the ptracer's
creds not PT_PTRACE_CAP").
Commit c70d9d809fde ("ptrace: Properly initialize ptracer_cred on
fork") in Linus tree fixes the issue. Tested with v4.11.4. Please
consider cherry-picking.
Thanks
Ralph
[ANNOUNCE] linux-4.11-ck1 / MuQSS CPU scheduler 0.155
These are patches designed to improve system responsiveness and interactivity with specific emphasis on the desktop, but configurable for any workload. The patchset is mainly centred around the Multiple Queue Skiplist Scheduler, MuQSS. linux-4.11-ck1 -ck1 patches: http://ck.kolivas.org/patches/4.0/4.11/4.11-ck1/ Git tree: https://github.com/ckolivas/linux/tree/4.11-ck MuQSS Download: http://ck.kolivas.org/patches/muqss/4.0/4.11/4.11-sched-MuQSS_155.patch Git tree: https://github.com/ckolivas/linux/tree/4.11-muqss 4.11-ck1 full patch list: 0001-Multiple-Queue-Skiplist-Scheduler-version-0.155-for-.patch 0002-Make-preemptible-kernel-default.patch 0003-Expose-vmsplit-for-our-pour-32-bit-users.patch 0004-Create-highres-timeout-variants-of-schedule_timeout-.patch 0005-Special-case-calls-of-schedule_timeout-1-to-use-the-.patch 0006-Convert-msleep-to-use-hrtimers-when-active.patch 0007-Replace-all-schedule-timeout-1-with-schedule_min_hrt.patch 0008-Replace-all-calls-to-schedule_timeout_interruptible-.patch 0009-Replace-all-calls-to-schedule_timeout_uninterruptibl.patch 0010-Make-hrtimer-granularity-and-minimum-hrtimeout-confi.patch 0011-Don-t-use-hrtimer-overlay-when-pm_freezing-since-som.patch 0012-Make-threaded-IRQs-optionally-the-default-which-can-.patch 0013-Reinstate-default-Hz-of-100-in-combination-with-MuQS.patch 0014-Make-writeback-throttling-default-enabled.patch 0015-Swap-sucks.patch 0016-BFQ-v8-for-linux-4.11.patch 0017-Make-BFQ-default-IO-scheduler.patch 0018-Add-ck1-version.patch For a brief description of each patch without trawling the git tree, each patch can be found as a quilt series here: http://ck.kolivas.org/patches/4.0/4.11/4.11-ck1/patches/ MuQSS 0.155 updates: Fixed syscall convention in the code for sched_setscheduler. Fixed copy to user error with max CPUs enabled. Changed skip lists to 25% probability of increased level (from 50%) scaling each CPU up to loads of 64k as a result. Minor preemption code tweak. 4.11-ck1 updates: Cleaned up the patchset. This was the most massive resync I think I can ever recall with the mainline kernel thanks to the complete restructuring of the scheduler code by Mingo. Fortunately there weren't that many actual changes to the scheduler itself that I needed to port but it was still a protracted effort. Probably the most amusing part of the resync was seeing my name mysteriously disappear from the credits of sched/core.c from mainline, although everyone's names were removed along with it. Given the size of this merge, it is possible there are build configurations that fail, so bear with me and post your config if that's the case. Hacking blog: http://ck-hack.blogspot.com/ Simple homepage: http://kernel.kolivas.org Enjoy! お楽しみ下さい -- -ck
Linux 4.11
So after that extra week with an rc8, things were pretty calm, and I'm much happier releasing a final 4.11 now. We still had various smaller fixes the last week, but nothing that made me go "hmm..". Shortlog appended for people who want to peruse the details, but it's a mix all over, with about half being drivers (networking dominates, but some sound fixlets too), with the rest being soem arch updates, generic networking, and filesystem (nfs[d]) fixes. But it's all really small, which is what I like to see the last week of the release cycle. And with this, the merge window is obviously open. I already have two pull request for 4.12 in my inbox, I expect that overnight I'll get a lot more. Linus --- Al Viro (4): orangefs_bufmap_copy_from_iovec(): fix EFAULT handling p9_client_readdir() fix fix nfs O_DIRECT advancing iov_iter too much fix a braino in ITER_PIPE iov_iter_revert() Alexander Kochetkov (1): net: phy: fix auto-negotiation stall due to unavailable interrupt Alexander Potapenko (1): net/packet: check length in getsockopt() called with PACKET_HDRLEN Andreas Kemnade (2): net: hso: fix module unloading net: hso: register netdev later to avoid a race condition Ansis Atteka (1): udp: disable inner UDP checksum offloads in IPsec case Arnaud Pouliquen (1): ASoC: STI: Fix null ptr deference in IRQ handler Arnd Bergmann (2): clk: sunxi-ng: always select CCU_GATE cpsw/netcp: refine cpts dependency Bert Kenward (1): sfc: tx ring can only have 2048 entries for all EF10 NICs Dan Carpenter (2): net: tc35815: move free after the dereference ravb: Double free on error in ravb_start_xmit() David Ahern (2): net: ipv6: send unsolicited NA if enabled for all interfaces net: ipv6: regenerate host route if moved to gc list David Howells (1): statx: Kill fd-with-NULL-path support in favour of AT_EMPTY_PATH David S. Miller (3): sparc64: Fill in rest of HAVE_REGS_AND_STACK_ACCESS_API sparc: Update syscall tables. Revert "phy: micrel: Disable auto negotiation on startup" David Sterba (1): btrfs: qgroup: move noisy underflow warning to debugging build Dmitry Torokhov (1): Input: i8042 - add Clevo P650RS to the i8042 reset list Dmitry V. Levin (1): uapi: change the type of struct statx_timestamp.tv_nsec to unsigned Eric Dumazet (2): tcp: do not underestimate skb->truesize in tcp_trim_head() net: adjust skb->truesize in ___pskb_trim() Eugenia Emantayev (1): net/mlx5e: Fix small packet threshold Florian Fainelli (3): net: dsa: b53: Include IMP/CPU port in dumb forwarding mode net: dsa: b53: Implement software reset for 58xx devices net: dsa: b53: Fix CPU port for 58xx devices Frederic Weisbecker (1): sched/cputime: Fix ksoftirqd cputime accounting regression Herbert Xu (1): macvlan: Fix device ref leak when purging bc_queue Ilan Tayari (1): net/mlx5e: Fix ETHTOOL_GRXCLSRLALL handling J. Bruce Fields (3): nfsd: check for oversized NFSv2/v3 arguments nfsd4: minor NFSv2/v3 write decoding cleanup nfsd: stricter decoding of write-like NFSv2/v3 ops James Cowgill (2): MIPS: Fix modversioning of _mcount symbol MIPS: Avoid BUG warning in arch_check_elf James Hogan (2): MIPS: cevt-r4k: Fix out-of-bounds array access MIPS: KGDB: Use kernel context for sleeping threads Jamie Bainbridge (1): ipv6: check raw payload size correctly in ioctl Janakarajan Natarajan (1): Prevent timer value 0 for MWAITX Jason A. Donenfeld (2): macsec: avoid heap overflow in skb_to_sgvec macsec: dynamically allocate space for sglist Johannes Thumshirn (1): scsi: return correct blkprep status code in case scsi_init_io() fails. Josh Poimboeuf (2): ftrace/x86: Fix triple fault with graph tracing and suspend-to-ram x86/build: convert function graph '-Os' error to warning Linus Torvalds (1): Linux 4.11 Maksim Salau (1): net: can: usb: gs_usb: Fix buffer on stack Maor Gottlieb (1): net/mlx5: Fix UAR memory leak Marcin Nowakowski (1): MIPS: generic: fix out-of-tree defconfig target builds Martin KaFai Lau (1): net/mlx5e: Fix race in mlx5e_sw_stats and mlx5e_vport_stats Mathias Kresin (1): MIPS: PCI: add controllers before the specified head Matt Redfearn (3): MIPS: Malta: Fix i8259 irqchip setup MIPS: KASLR: Add missing header files MIPS: smp-cps: Fix potentially uninitialised value of core Michael Kerrisk (man-pages) (1): statx: correct error handling of NULL pathname Mohamad Haj Yahia (1): net/mlx5: Fix driver load bad flow when having fw initializing timeout Mousumi Jana (1): ASoC: topology: Fix to store enum text values Myungho Jung (1): net: core: Prevent from dereferencing null pointer when re
Linux 4.11-rc8
ith Busch (1): genirq/affinity: Fix calculating vectors to assign Linus Torvalds (1): Linux 4.11-rc8 Mel Gorman (1): Revert "mm, page_alloc: only use per-cpu allocator for irq-safe requests" Michael Ellerman (1): powerpc/64: Fix HMI exception on LE with CONFIG_RELOCATABLE=y Michal Hocko (1): mm: make mm_percpu_wq non freezable Mike Maloney (1): selftests/net: Fixes psock_fanout CBPF test case Ming Lei (2): block: respect BLK_MQ_F_NO_SCHED mtip32xx: pass BLK_MQ_F_NO_SCHED Namhyung Kim (2): ftrace: Fix function pid filter on instances selftests: ftrace: Add a testcase for function PID filter Nikolay Aleksandrov (1): ip6mr: fix notification device destruction Nitin Gupta (1): sparc64: Fix hugepage page table free Olga Kornievskaia (1): nfsd: fix oops on unsupported operation Rabin Vincent (1): mm: prevent NR_ISOLATE_* stats from going negative Ravi Bangoria (1): powerpc/kprobe: Fix oops when kprobed on 'stdu' instruction Richard Weinberger (2): ubifs: Fix memory leak in error path in ubifs_mknod ubifs: Fix O_TMPFILE corner case in ubifs_link() Sachin Prabhu (1): cifs: Do not send echoes before Negotiate is complete Sean Wang (2): net: ethernet: mediatek: fix inconsistency between TXD and the used buffer net: ethernet: mediatek: fix inconsistency of port number carried in TXD Sebastian Siewior (1): ubi/upd: Always flush after prepared for an update Sekhar Nori (1): MAINTAINERS: update entry for TI's CPSW driver Sergei Shtylyov (1): sh_eth: unmap DMA buffers when freeing rings Steven Rostedt (VMware) (3): selftests: ftrace: Add check for function-fork before running pid filter test tracing: Allocate the snapshot buffer before enabling probe ring-buffer: Have ring_buffer_iter_empty() return true when empty Thorsten Leemhuis (1): Input: elantech - add Fujitsu Lifebook E547 to force crc_enabled Tobias Regnery (2): clk: sunxi-ng: fix build error without CONFIG_RESET_CONTROLLER clk: sunxi-ng: fix build failure in ccu-sun9i-a80 driver Tushar Dave (1): netpoll: Check for skb->queue_mapping Vishal Verma (1): x86/mce: Make the MCE notifier a blocking one WANG Cong (1): ipv4: fix a deadlock in ip_ra_control Willem de Bruijn (1): net-timestamp: avoid use-after-free in ip_recv_error Wolfgang Bumiller (1): net sched actions: allocate act cookie early Yuejie Shi (1): af_key: Add lock to key dump [email protected] (4): qed: Fix possible error in populating max_tc field. qed: Fix sending an invalid PFC error mask to MFW. qed: Fix possible system hang in the dcbnl-getdcbx() path. qed: Fix issue in populating the PFC config paramters.
Linux 4.11: Reported regressions as of Friday, 2017-04-21
Hi! Find below my fourth regression report for Linux 4.11. It lists 10 regressions I'm currently aware of. 7 regressions mentioned in last weeks report got fixed. As always: Are you aware of any other regressions? Then please let me know (simply CC [email protected]). And please tell me if there is anything in the report that shouldn't be there. Ciao, Thorsten P.S.: Thx to all those that CCed me on regression reports or provided other input, it makes compiling these reports a whole lot easier! == Current regressions == Desc: Client system gets spammed with 'NFSv4 Callback' kthreads - eventually causing NFS shares to become unresponsive Repo: 2017-04-17 https://bugzilla.kernel.org/show_bug.cgi?id=195449 Stat: n/a Note: quite new, needs to get forwarded to the network people Desc: boot problems when virtio-scsi is used Repo: 2017-04-19 https://www.mail-archive.com/[email protected]/msg1380561.html Stat: 2017-04-20 https://www.mail-archive.com/[email protected]/msg1381637.html Note: patch heading mainline Desc: unable to handle kernel NULL pointer dereference, mtip_irq_handler+0x262/0x3c0 [mtip32xx] Repo: 2017-04-12 https://bugzilla.kernel.org/show_bug.cgi?id=195429 Stat: n/a Note: not entirely clear if this is a regression, but bhelgaas is looking into it Desc: tytso: systemd doesn't see most devices Repo: 2017-04-11 https://www.mail-archive.com/[email protected]/msg1375255.html Stat: 2017-04-12 https://www.mail-archive.com/[email protected]/msg1375851.html Note: heisenbug? Desc: crash since 617f01211baf ("8139too: use napi_complete_done()") Repo: 2017-04-07 https://www.mail-archive.com/[email protected]/msg162162.html Stat: 2017-04-08 https://www.mail-archive.com/[email protected]/msg162285.html Note: there is a patch in that thread, but it afaics is not heading mainline and the discussion stalled Desc: Busy softirq can cause userspace not to be scheduled Repo: 2017-03-28 https://www.mail-archive.com/[email protected]/msg1363884.html Stat: 2017-04-20 https://www.mail-archive.com/[email protected]/msg1381585.html Note: Frederic: "working on reproducing that one" Desc: Commit d8514d8edb5b ("ovl: copy up regular file using O_TMPFILE") breaks ubifs Repo: 2017-03-28 https://www.mail-archive.com/[email protected]/msg1363879.html Stat: 2017-04-17 https://www.mail-archive.com/[email protected]/msg1378740.html Note: Patch hopefully heading upstream soon Desc: pine64 defconfig: WARNING: CPU: 0 PID: 86 at drivers/base/dd.c:349 driver_probe_device+0x258/0x2c0 Repo: 2017-03-25 https://bugzilla.kernel.org/show_bug.cgi?id=195037 https://www.mail-archive.com/[email protected]/msg1368488.html Stat: 2017-04-18 https://www.mail-archive.com/[email protected]/msg1379209.html Note: André doesnt have a clue and needs someone with insights devm and devres; seems to be gone in -next Desc: NVMe APST: Samsung NVMe sudden controller death Repo: 2017-03-18 https://bugzilla.kernel.org/show_bug.cgi?id=195039 https://bugzilla.kernel.org/show_bug.cgi?id=194921 Stat: 2017-04-20 https://www.mail-archive.com/[email protected]/msg1381954.html Note: blacklist update heading mainline Desc: Perf regression after enabling nvme APST Repo: 2017-03-17 https://lkml.org/lkml/2017/3/17/177 Stat: 2017-04-20 https://lkml.org/lkml/2017/3/20/998 Note: stalled == Stalled, waiting for feedback from reporter == Desc: kvm: workqueue lockup Repo: 2017-03-14 https://bugzilla.kernel.org/show_bug.cgi?id=194883 Stat: 2017-03-27 https://bugzilla.kernel.org/show_bug.cgi?id=194883#c1 Note: asked reporter if issue still present in RC4 Desc: general protection fault: inet6_fill_ifaddr+0x6c/0x230 Repo: 2017-03-11 https://bugzilla.kernel.org/show_bug.cgi?id=194849 Stat: 2017-03-13 https://bugzilla.kernel.org/show_bug.cgi?id=194849#c1 Note: Cong Wang asked reporter for details, didn't get any reply yet Desc: 4.11 PowerMac G5 970MP: [drm:.r600_ring_test [radeon]] *ERROR* radeon: ring 0 test failed (scratch(0x8504)=0xCAFEDEAD Repo: 2017-03-24 https://bugs.freedesktop.org/show_bug.cgi?id=99851#c26 Stat: n/a Note: stalled; looks like reporter (who does not see the problem in 4.10) could need some help bisecting == Going to be removed from the list == Desc: i915 gpu hangs under load (2) Repo: 2017-03-22 https://www.mail-archive.com/[email protected]/msg1372182.html Stat: 2017-04-07 https://www.mail-archive.com/[email protected]/msg1372182.html Note: Andrea saw issues and sent some patches that were discussed; some were applied, others discussed, but then the discussion stalled; I assume it's fixed, as Andrea knows how all this works Desc: Warning since RC4: sed_opal:OPAL: Error on step function: 0 with error -95: Unknown Error Repo: 2017-04-07 https://bugzilla.kernel.org/show_bug.cgi?id=195277 St
Linux 4.11-rc7
einstantiation error checking Icenowy Zheng (1): arm64: allwinner: a64: add pmu0 regs for USB PHY Ido Schimmel (2): bridge: implement missing ndo_uninit() bridge: netlink: register netdevice before executing changelink Ilia Mirkin (2): drm/nouveau/mpeg: mthd returns true on success now drm/nouveau/mmu/nv4a: use nv04 mmu rather than the nv44 one Jan Beulich (1): ia64: restore symbol versions for symbols defined in assembly Jiri Kosina (1): Revert "HID: rmi: Handle all Synaptics touchpads using hid-rmi" Jiri Olsa (1): x86/intel_rdt: Fix locking in rdtgroup_schemata_write() Joerg Roedel (1): x86/signals: Fix lower/upper bound reporting in compat siginfo Johannes Berg (2): bpf: reference may_access_skb() from __bpf_prog_run() net: xdp: don't export dev_change_xdp_fd() Jonathan Neuschäfer (1): drm/udl: Fix unaligned memory access in udl_render_hline Joonas Lahtinen (1): drm/i915: Don't call synchronize_rcu_expedited under struct_mutex Juergen Gross (1): xen, fbfront: fix connecting to backend Kees Cook (1): mm: Tighten x86 /dev/mem with zeroing reads Keith Busch (2): irq/affinity: Fix CPU spread for unbalanced nodes irq/affinity: Fix extra vecs calculation Kirill A. Shutemov (5): thp: reduce indentation level in change_huge_pmd() thp: fix MADV_DONTNEED vs. numa balancing race mm: drop unused pmdp_huge_get_and_clear_notify() thp: fix MADV_DONTNEED vs. MADV_FREE race thp: fix MADV_DONTNEED vs clear soft dirty race Len Brown (6): tools/power turbostat: bugfix: GFXMHz column not changing tools/power turbostat: show missing Core and GFX power on SKL and KBL tools/power turbostat: enable package THERM_INTERRUPT dump tools/power turbostat: update HWP dump to decimal from hex tools/power turbostat: fix impossibly large CPU%c1 value tools/power turbostat: update version number Linus Torvalds (2): vfs: don't do RCU lookup of empty pathnames Linux 4.11-rc7 Liping Zhang (6): netfilter: ctnetlink: using bit to represent the ct event netfilter: ctnetlink: make it safer when checking the ct helper name netfilter: make it safer during the inet6_dev->addr_list traversal netfilter: ctnetlink: skip dumping expect when nfct_help(ct) is NULL netfilter: nf_ct_expect: use proper RCU list traversal/update APIs netfilter: nft_hash: do not dump the auto generated seed Liu Bo (3): Btrfs: fix invalid dereference in btrfs_retry_endio Btrfs: fix segmentation fault when doing dio read Btrfs: fix potential use-after-free for cloned bio Manish Narani (1): usb: gadget: Correct usb EP argument for BOT status request Marc Zyngier (1): virtio-pci: Remove affinity hint before freeing the interrupt Mark Syms (1): CIFS: handle guest access errors to Windows shares Markus Marb (1): can: ifi: use correct register to read rx status Markus Trippelsdorf (1): x86/debug: Fix the printk() debug output of signal_fault(), do_trap() and do_general_protection() Martin Brandenburg (1): orangefs: free superblock when mount fails Martin K. Petersen (2): scsi: sr: Sanity check returned mode data scsi: sd: Fix capacity calculation with 32-bit sector_t Martin Kepplinger (1): mailmap: add Martin Kepplinger's email Mathias Krause (1): x86/vdso: Ensure vdso32_enabled gets set to valid values only Matthew Auld (2): drm/i915/perf: destroy stream on sample_flags mismatch drm/i915/perf: remove user triggerable warn Mauricio Faria de Oliveira (1): scsi: ipr: do not set DID_PASSTHROUGH on CHECK CONDITION Michael S. Tsirkin (9): virtio_net: enable big packets for large MTU values virtio: allow drivers to validate features virtio_net: clear MTU when out of range virtio_console: fix uninitialized variable use Revert "virtio_pci: fix out of bound access for msix_names" Revert "virtio_pci: simplify MSI-X setup" Revert "virtio_pci: don't duplicate the msix_enable flag in struct pci_dev" Revert "virtio_pci: use shared interrupts for virtqueues" Revert "virtio_pci: remove struct virtio_pci_vq_info" Mika Westerberg (1): pinctrl: cherryview: Add a quirk to make Acer Chromebook keyboard work again Mike Christie (1): target: Fix ALUA transition state race between multiple initiators Mike Kravetz (1): hugetlbfs: fix offset overflow in hugetlbfs mmap Mikulas Patocka (1): parisc: fix bugs in pa_memcpy Min He (1): drm/i915/gvt: set the correct default value of CTX STATUS PTR Minchan Kim (3): zram: fix operator precedence to get offset zram: do not use copy_page with non-page aligned address zsmalloc: expand class bit Ming Lei (1): block: fix bio_will_gap() fo
RE: [Regression Linux 4.11] TPM module not loaded anymore
Dear Robert, Thank you for your reply. On 2017-04-12 23:49, Moore, Robert wrote: On 2017-04-12 17:54, Moore, Robert wrote: > And probably the dmesg if error messages appear in there. Linux doesn’t log any messages, as the `tpm` module doesn’t load. Please find the output of `sudo acpidump` attached. […] Do you have any idea what control method(s) are executing? The DSDT and SSDT in the acpidump load fine here, and all predefined control methods in these tables execute OK. Sorry, I don’t know what’s done. We need to root-cause this problem, as a simple revert will break the customers that the fix was intended for in the first place. I know, but I have no idea how to root-cause this. If nothing can be found, a revert is required by Linux’ no-regression-policy. Kind regards, Paul
RE: [Regression Linux 4.11] TPM module not loaded anymore
> -Original Message- > From: Paul Menzel [mailto:[email protected]] > Sent: Wednesday, April 12, 2017 2:27 PM > To: Moore, Robert > Cc: Jarkko Sakkinen ; Maciej S. > Szmigiero ; [email protected]; > Arthur Heymans ; [email protected]; > [email protected]; Zheng, Lv ; Wysocki, Rafael J > ; [email protected] > Subject: RE: [Regression Linux 4.11] TPM module not loaded anymore > > Dear Robert, > > > Thank you for looking into this. > > > On 2017-04-12 17:54, Moore, Robert wrote: > > And probably the dmesg if error messages appear in there. > > Linux doesn’t log any messages, as the `tpm` module doesn’t load. Please > find the output of `sudo acpidump` attached. > > […] > [Moore, Robert] Do you have any idea what control method(s) are executing? The DSDT and SSDT in the acpidump load fine here, and all predefined control methods in these tables execute OK. We need to root-cause this problem, as a simple revert will break the customers that the fix was intended for in the first place. Bob > > Kind regards, > > Paul > > > PS: Doesn’t your mail client support to easily reply in interleaved > style?
RE: [Regression Linux 4.11] TPM module not loaded anymore
Dear Robert, Thank you for looking into this. On 2017-04-12 17:54, Moore, Robert wrote: And probably the dmesg if error messages appear in there. Linux doesn’t log any messages, as the `tpm` module doesn’t load. Please find the output of `sudo acpidump` attached. […] Kind regards, Paul PS: Doesn’t your mail client support to easily reply in interleaved style?RSD @ 0x000F0800 : 52 53 44 20 50 54 52 20 05 43 4F 52 45 20 20 02 RSD PTR .CORE . 0010: 30 50 72 7F 24 00 00 00 E0 50 72 7F 00 00 00 00 0Pr.$Pr. 0020: BB 00 00 00 RSDT @ 0x7F725030 : 52 53 44 54 3C 00 00 00 01 23 43 4F 52 45 20 20 RSDT<#CORE 0010: 43 4F 52 45 42 4F 4F 54 00 00 00 00 43 4F 52 45 COREBOOTCORE 0020: 00 00 00 00 E0 80 72 7F E0 81 72 7F 10 87 72 7F ..r...r...r. 0030: 50 87 72 7F 90 87 72 7F 00 88 72 7F P.r...r...r. XSDT @ 0x7F7250E0 : 58 53 44 54 54 00 00 00 01 05 43 4F 52 45 20 20 XSDTT.CORE 0010: 43 4F 52 45 42 4F 4F 54 00 00 00 00 43 4F 52 45 COREBOOTCORE 0020: 00 00 00 00 E0 80 72 7F 00 00 00 00 E0 81 72 7F ..r...r. 0030: 00 00 00 00 10 87 72 7F 00 00 00 00 50 87 72 7F ..r.P.r. 0040: 00 00 00 00 90 87 72 7F 00 00 00 00 00 88 72 7F ..r...r. 0050: 00 00 00 00 DSDT @ 0x7F725280 : 44 53 44 54 58 2E 00 00 03 18 43 4F 52 45 76 34 DSDTX.COREv4 0010: 43 4F 52 45 42 4F 4F 54 19 04 09 20 49 4E 54 4C COREBOOT... INTL 0020: 26 09 14 20 10 8F 00 00 5C 00 08 4E 56 53 41 0C &.. \..NVSA. 0030: 80 E9 7F 7F 14 4F 04 5F 50 54 53 01 5C 2F 05 5F .O._PTS.\/._ 0040: 53 42 5F 50 43 49 30 4C 50 43 42 45 43 5F 5F 4D SB_PCI0LPCBEC__M 0050: 55 54 45 01 5C 2F 05 5F 53 42 5F 50 43 49 30 4C UTE.\/._SB_PCI0L 0060: 50 43 42 45 43 5F 5F 55 53 42 50 00 5C 2F 05 5F PCBEC__USBP.\/._ 0070: 53 42 5F 50 43 49 30 4C 50 43 42 45 43 5F 5F 52 SB_PCI0LPCBEC__R 0080: 41 44 49 00 14 18 5F 57 41 4B 01 A0 05 93 68 0A ADI..._WAKh. 0090: 03 A0 05 93 68 0A 04 A4 12 04 02 00 00 10 1F 5F h.._ 00A0: 53 42 5F 14 19 5F 49 4E 49 00 47 4F 53 5F A0 0E SB_.._INI.GOS_.. 00B0: 90 93 4F 53 59 53 0B D1 07 4D 50 45 4E 08 50 49 ..OSYS...MPEN.PI 00C0: 43 4D 00 08 44 53 45 4E 01 5B 80 47 4E 56 53 00 CM..DSEN.[.GNVS. 00D0: 4E 56 53 41 0B 00 01 5B 81 4E 22 47 4E 56 53 01 NVSA...[.N"GNVS. 00E0: 4F 53 59 53 10 53 4D 49 46 08 50 52 4D 30 08 50 OSYS.SMIF.PRM0.P 00F0: 52 4D 31 08 53 43 49 46 08 50 52 4D 32 08 50 52 RM1.SCIF.PRM2.PR 0100: 4D 33 08 4C 43 4B 46 08 50 52 4D 34 08 50 52 4D M3.LCKF.PRM4.PRM 0110: 35 08 50 38 30 44 20 4C 49 44 53 08 50 57 52 53 5.P80D LIDS.PWRS 0120: 08 44 42 47 53 08 4C 49 4E 58 08 44 43 4B 4E 08 .DBGS.LINX.DCKN. 0130: 41 43 54 54 08 50 53 56 54 08 54 43 31 56 08 54 ACTT.PSVT.TC1V.T 0140: 43 32 56 08 54 53 50 56 08 43 52 54 54 08 44 54 C2V.TSPV.CRTT.DT 0150: 53 45 08 44 54 53 31 08 44 54 53 32 08 00 08 42 SE.DTS1.DTS2...B 0160: 4E 55 4D 08 42 30 53 43 08 42 31 53 43 08 42 32 NUM.B0SC.B1SC.B2 0170: 53 43 08 42 30 53 53 08 42 31 53 53 08 42 32 53 SC.B0SS.B1SS.B2S 0180: 53 08 00 18 41 50 49 43 08 4D 50 45 4E 08 50 43 S...APIC.MPEN.PC 0190: 50 30 08 50 43 50 31 08 50 50 43 4D 08 00 28 4E P0.PCP1.PPCM..(N 01A0: 41 54 50 08 43 4D 41 50 08 43 4D 42 50 08 4C 50 ATP.CMAP.CMBP.LP 01B0: 54 50 08 46 44 43 50 08 52 46 44 56 08 48 4F 54 TP.FDCP.RFDV.HOT 01C0: 4B 08 52 54 43 46 08 55 54 49 4C 08 41 43 49 4E K.RTCF.UTIL.ACIN 01D0: 08 49 47 44 53 08 54 4C 53 54 08 43 41 44 4C 08 .IGDS.TLST.CADL. 01E0: 50 41 44 4C 08 43 53 54 45 10 4E 53 54 45 10 53 PADL.CSTE.NSTE.S 01F0: 53 54 45 10 4E 44 49 44 08 44 49 44 31 20 44 49 STE.NDID.DID1 DI 0200: 44 32 20 44 49 44 33 20 44 49 44 34 20 44 49 44 D2 DID3 DID4 DID 0210: 35 20 00 48 04 42 4C 43 53 08 42 52 54 4C 08 4F 5 .H.BLCS.BRTL.O 0220: 44 44 53 08 00 38 41 4C 53 45 08 41 4C 41 46 08 DDS..8ALSE.ALAF. 0230: 4C 4C 4F 57 08 4C 48 49 48 08 00 30 45 4D 41 45 LLOW.LHIH..0EMAE 0240: 08 45 4D 41 50 10 45 4D 41 4C 10 00 28 4D 45 46 .EMAP.EMAL..(MEF 0250: 45 08 00 48 04 54 50 4D 50 08 54 50 4D 45 08 00 E..H.TPMP.TPME.. 0260: 40 04 47 54 46 30 38 47 54 46 31 38 47 54 46 32 @.GTF08GTF18GTF2 0270: 38 49 44 45 4D 08 49 44 45 54 08 00 38 41 53 4C 8IDEM.IDET..8ASL 0280: 42 20 49 42 54 54 08 49 50 41 54 08 49 54 56 46 B IBTT.IPAT.ITVF 0290: 08 49 54 56 4D 08 49 50 53 43 08 49 42 4C 43 08 .ITVM.IPSC.IBLC. 02A0: 49 42 49 41 08 49 53 53 43 08 49 34 30 39 08 49 IBIA.ISSC.I409.I 02B0: 35 30 39 08 49 36 30 39 08 49 37 30 39 08 49 44 509.I609.I709.ID 02C0: 4D 4D 08 49 44 4D 53 08 49 46 31 45 08 48 56 43 MM.IDMS.IF1E.HVC 02D0: 4F 08 4E 58 44 31 20 4E 58 44 32 20 4E 58 44 33 O.NXD1 NXD2 NXD3 02E0: 20 4E 58 44 34 20 4E 58 44 35 20 4E 58 44 36 20 NXD4 NXD5 NXD6 02F0: 4E 58 44 37 20 4E 58 44 38 20 00 40 04 44 4F 43 NXD7 NXD8 [email protected] 0300: 4B 08 42 54 45 4E 08
RE: [Regression Linux 4.11] TPM module not loaded anymore (was: Regression between Linux 3.16 and 4.8/4.9 on Lenovo X60 with coreboot)
And probably the dmesg if error messages appear in there. > -Original Message- > From: Moore, Robert > Sent: Wednesday, April 12, 2017 8:53 AM > To: 'Jarkko Sakkinen' ; Paul Menzel > > Cc: Maciej S. Szmigiero ; linux- > [email protected]; Arthur Heymans ; tpmdd- > [email protected]; [email protected]; Zheng, Lv > ; Wysocki, Rafael J > Subject: RE: [Regression Linux 4.11] TPM module not loaded anymore (was: > Regression between Linux 3.16 and 4.8/4.9 on Lenovo X60 with coreboot) > > Please post the acpidump for this machine so we can analyze the actual > AML byte code. > Thanks. > > > > -Original Message- > > From: Jarkko Sakkinen [mailto:[email protected]] > > Sent: Tuesday, April 11, 2017 3:58 PM > > To: Paul Menzel > > Cc: Moore, Robert ; Maciej S. Szmigiero > > ; [email protected]; Arthur > > Heymans ; [email protected]; > > [email protected]; Zheng, Lv ; Wysocki, Rafael J > > > > Subject: Re: [Regression Linux 4.11] TPM module not loaded anymore > (was: > > Regression between Linux 3.16 and 4.8/4.9 on Lenovo X60 with coreboot) > > > > On Sun, Apr 09, 2017 at 07:34:43PM +0200, Paul Menzel wrote: > > > Dear Linux folks, > > > > > > > > > It turns out that stricter checks in the ACPI subsystem, introduced > > > in commit 57707a9a77 (ACPICA: Resources: Not a valid resource if > > > buffer length too long) [1], cause the TPM module not to be loaded > > > anymore on the Lenovo X60 with coreboot [2]. > > > > > > Am Freitag, den 07.04.2017, 22:58 +0200 schrieb Paul Menzel: > > > > On 2017-04-07 22:13, Jarkko Sakkinen wrote: > > > > > On Thu, Apr 06, 2017 at 01:10:13PM -0600, Jason Gunthorpe wrote: > > > > >> On Thu, Apr 06, 2017 at 08:26:22PM +0200, Paul Menzel wrote: > > > > >> > >We added direct ACPI binding to the driver in addition to > > > > >> > >PNP, so if you have an ACPI table it goes down that path and > > > > >> > >does some additional validation of what is in the TPM. The > > > > >> > >BIOS must provide a acpi_dev_resource_memory and a > > > > >> > >ACPI_SIG_TPM2 for the ACPI entry at a minimum. > > > > >> > > > > > >> > Is it correct, that this is added in/for 4.11, so just > > > > >> > recently? Testing with Linux 4.10.8, everything is detected > > just fine. > > > > >> > > > > >> No, it is quite a bit older.. And it should only go for TPM2, > > > > >> which I don't think you have?? > > > > >> > > > > >> Maybe Jarkko has a guess, but sure sounds like something is > > > > >> recently broken in 4.11 > > > > > > > > > > I'll come back to this. I have to re-read the whole mail thread > > > > > to get back into the context. Lots of multitasking because of > > > > > release and so forth. Sorry for the latency! > > > > > > > > I started bisecting this issue. This is the current state. > > > > > > […] > > > > > > Here are the results. > > > > > > ``` > > > git bisect log > > > # bad: [7a771ceac771d009f7203c40b256b0608d7ea2f8] Merge tag > > > 'dm-4.11-changes' of > > > git://git.kernel.org/pub/scm/linux/kernel/git/device-mapper/linux-dm > > > # good: [c470abd4fde40ea6a0846a2beab642a578c0b8cd] Linux 4.10 git > > > bisect start 'HEAD' 'v4.10' > > > # good: [b3de5ad688f0f52457e73767f95a640ab4158d0d] Merge tag > > > 'regmap-v4.11' of > > > git://git.kernel.org/pub/scm/linux/kernel/git/broonie/regmap > > > git bisect good b3de5ad688f0f52457e73767f95a640ab4158d0d > > > # bad: [fd4a61e08aa79f2b7835b25c6f94f27bd2d65990] sched/core: Fix > > > build paravirt build on arm and arm64 git bisect bad > > > fd4a61e08aa79f2b7835b25c6f94f27bd2d65990 > > > # good: [7aa7d608112baf63a0b1278955f9619427373807] Merge tag > > > 'leds_for_4.11' of > > > git://git.kernel.org/pub/scm/linux/kernel/git/j.anaszewski/linux-led > > > s git bisect good 7aa7d608112baf63a0b1278955f9619427373807 > > > # good: [02c3de1105228e367320e7fdeffbf511904f398c] Merge tag > > > 'pm-4.11-rc1' of > > > git://git.kernel.org/pub/scm/linux/kernel/git/rafael/linux-pm > > > git bisect good 02c3de1105228e367320e7fdeffbf5119
RE: [Regression Linux 4.11] TPM module not loaded anymore (was: Regression between Linux 3.16 and 4.8/4.9 on Lenovo X60 with coreboot)
Please post the acpidump for this machine so we can analyze the actual AML byte code. Thanks. > -Original Message- > From: Jarkko Sakkinen [mailto:[email protected]] > Sent: Tuesday, April 11, 2017 3:58 PM > To: Paul Menzel > Cc: Moore, Robert ; Maciej S. Szmigiero > ; [email protected]; Arthur > Heymans ; [email protected]; > [email protected]; Zheng, Lv ; Wysocki, Rafael J > > Subject: Re: [Regression Linux 4.11] TPM module not loaded anymore (was: > Regression between Linux 3.16 and 4.8/4.9 on Lenovo X60 with coreboot) > > On Sun, Apr 09, 2017 at 07:34:43PM +0200, Paul Menzel wrote: > > Dear Linux folks, > > > > > > It turns out that stricter checks in the ACPI subsystem, introduced in > > commit 57707a9a77 (ACPICA: Resources: Not a valid resource if buffer > > length too long) [1], cause the TPM module not to be loaded anymore on > > the Lenovo X60 with coreboot [2]. > > > > Am Freitag, den 07.04.2017, 22:58 +0200 schrieb Paul Menzel: > > > On 2017-04-07 22:13, Jarkko Sakkinen wrote: > > > > On Thu, Apr 06, 2017 at 01:10:13PM -0600, Jason Gunthorpe wrote: > > > >> On Thu, Apr 06, 2017 at 08:26:22PM +0200, Paul Menzel wrote: > > > >> > >We added direct ACPI binding to the driver in addition to PNP, > > > >> > >so if you have an ACPI table it goes down that path and does > > > >> > >some additional validation of what is in the TPM. The BIOS > > > >> > >must provide a acpi_dev_resource_memory and a ACPI_SIG_TPM2 > > > >> > >for the ACPI entry at a minimum. > > > >> > > > > >> > Is it correct, that this is added in/for 4.11, so just > > > >> > recently? Testing with Linux 4.10.8, everything is detected > just fine. > > > >> > > > >> No, it is quite a bit older.. And it should only go for TPM2, > > > >> which I don't think you have?? > > > >> > > > >> Maybe Jarkko has a guess, but sure sounds like something is > > > >> recently broken in 4.11 > > > > > > > > I'll come back to this. I have to re-read the whole mail thread to > > > > get back into the context. Lots of multitasking because of release > > > > and so forth. Sorry for the latency! > > > > > > I started bisecting this issue. This is the current state. > > > > […] > > > > Here are the results. > > > > ``` > > git bisect log > > # bad: [7a771ceac771d009f7203c40b256b0608d7ea2f8] Merge tag > > 'dm-4.11-changes' of > > git://git.kernel.org/pub/scm/linux/kernel/git/device-mapper/linux-dm > > # good: [c470abd4fde40ea6a0846a2beab642a578c0b8cd] Linux 4.10 git > > bisect start 'HEAD' 'v4.10' > > # good: [b3de5ad688f0f52457e73767f95a640ab4158d0d] Merge tag > > 'regmap-v4.11' of > > git://git.kernel.org/pub/scm/linux/kernel/git/broonie/regmap > > git bisect good b3de5ad688f0f52457e73767f95a640ab4158d0d > > # bad: [fd4a61e08aa79f2b7835b25c6f94f27bd2d65990] sched/core: Fix > > build paravirt build on arm and arm64 git bisect bad > > fd4a61e08aa79f2b7835b25c6f94f27bd2d65990 > > # good: [7aa7d608112baf63a0b1278955f9619427373807] Merge tag > > 'leds_for_4.11' of > > git://git.kernel.org/pub/scm/linux/kernel/git/j.anaszewski/linux-leds > > git bisect good 7aa7d608112baf63a0b1278955f9619427373807 > > # good: [02c3de1105228e367320e7fdeffbf511904f398c] Merge tag > > 'pm-4.11-rc1' of > > git://git.kernel.org/pub/scm/linux/kernel/git/rafael/linux-pm > > git bisect good 02c3de1105228e367320e7fdeffbf511904f398c > > # bad: [6c24337f22115d669e24ce990842dab667371b4d] Merge tag > > 'fscrypt-for-linus' of > > git://git.kernel.org/pub/scm/linux/kernel/git/tytso/fscrypt > > git bisect bad 6c24337f22115d669e24ce990842dab667371b4d > > # bad: [a74d1cafc22e100a9b59c50943ca09c37e03dce8] Merge branches > 'acpi-bus', 'acpi-sleep' and 'acpi-processor' > > git bisect bad a74d1cafc22e100a9b59c50943ca09c37e03dce8 > > # bad: [ce87e09dd88c61f9088768a7708828423549725c] ACPICA: Parser: > > Allow method invocations as target operands git bisect bad > > ce87e09dd88c61f9088768a7708828423549725c > > # good: [0fc5e8f4e4b33ddfa1d1d673fcd420d6e13eb076] ACPICA: Hardware: > > Add sleep register hooks git bisect good > > 0fc5e8f4e4b33ddfa1d1d673fcd420d6e13eb076 > > # good: [a654b8ca6d28736995de767ba62e801fd806a3b2] ACPICA: > > Disassembler: Add Switch/Case
RE: [Regression Linux 4.11] TPM module not loaded anymore (was: Regression between Linux 3.16 and 4.8/4.9 on Lenovo X60 with coreboot)
I'll try to look at it today Bob > -Original Message- > From: Jarkko Sakkinen [mailto:[email protected]] > Sent: Tuesday, April 11, 2017 3:58 PM > To: Paul Menzel > Cc: Moore, Robert ; Maciej S. Szmigiero > ; [email protected]; Arthur > Heymans ; [email protected]; > [email protected]; Zheng, Lv ; Wysocki, Rafael J > > Subject: Re: [Regression Linux 4.11] TPM module not loaded anymore (was: > Regression between Linux 3.16 and 4.8/4.9 on Lenovo X60 with coreboot) > > On Sun, Apr 09, 2017 at 07:34:43PM +0200, Paul Menzel wrote: > > Dear Linux folks, > > > > > > It turns out that stricter checks in the ACPI subsystem, introduced in > > commit 57707a9a77 (ACPICA: Resources: Not a valid resource if buffer > > length too long) [1], cause the TPM module not to be loaded anymore on > > the Lenovo X60 with coreboot [2]. > > > > Am Freitag, den 07.04.2017, 22:58 +0200 schrieb Paul Menzel: > > > On 2017-04-07 22:13, Jarkko Sakkinen wrote: > > > > On Thu, Apr 06, 2017 at 01:10:13PM -0600, Jason Gunthorpe wrote: > > > >> On Thu, Apr 06, 2017 at 08:26:22PM +0200, Paul Menzel wrote: > > > >> > >We added direct ACPI binding to the driver in addition to PNP, > > > >> > >so if you have an ACPI table it goes down that path and does > > > >> > >some additional validation of what is in the TPM. The BIOS > > > >> > >must provide a acpi_dev_resource_memory and a ACPI_SIG_TPM2 > > > >> > >for the ACPI entry at a minimum. > > > >> > > > > >> > Is it correct, that this is added in/for 4.11, so just > > > >> > recently? Testing with Linux 4.10.8, everything is detected > just fine. > > > >> > > > >> No, it is quite a bit older.. And it should only go for TPM2, > > > >> which I don't think you have?? > > > >> > > > >> Maybe Jarkko has a guess, but sure sounds like something is > > > >> recently broken in 4.11 > > > > > > > > I'll come back to this. I have to re-read the whole mail thread to > > > > get back into the context. Lots of multitasking because of release > > > > and so forth. Sorry for the latency! > > > > > > I started bisecting this issue. This is the current state. > > > > […] > > > > Here are the results. > > > > ``` > > git bisect log > > # bad: [7a771ceac771d009f7203c40b256b0608d7ea2f8] Merge tag > > 'dm-4.11-changes' of > > git://git.kernel.org/pub/scm/linux/kernel/git/device-mapper/linux-dm > > # good: [c470abd4fde40ea6a0846a2beab642a578c0b8cd] Linux 4.10 git > > bisect start 'HEAD' 'v4.10' > > # good: [b3de5ad688f0f52457e73767f95a640ab4158d0d] Merge tag > > 'regmap-v4.11' of > > git://git.kernel.org/pub/scm/linux/kernel/git/broonie/regmap > > git bisect good b3de5ad688f0f52457e73767f95a640ab4158d0d > > # bad: [fd4a61e08aa79f2b7835b25c6f94f27bd2d65990] sched/core: Fix > > build paravirt build on arm and arm64 git bisect bad > > fd4a61e08aa79f2b7835b25c6f94f27bd2d65990 > > # good: [7aa7d608112baf63a0b1278955f9619427373807] Merge tag > > 'leds_for_4.11' of > > git://git.kernel.org/pub/scm/linux/kernel/git/j.anaszewski/linux-leds > > git bisect good 7aa7d608112baf63a0b1278955f9619427373807 > > # good: [02c3de1105228e367320e7fdeffbf511904f398c] Merge tag > > 'pm-4.11-rc1' of > > git://git.kernel.org/pub/scm/linux/kernel/git/rafael/linux-pm > > git bisect good 02c3de1105228e367320e7fdeffbf511904f398c > > # bad: [6c24337f22115d669e24ce990842dab667371b4d] Merge tag > > 'fscrypt-for-linus' of > > git://git.kernel.org/pub/scm/linux/kernel/git/tytso/fscrypt > > git bisect bad 6c24337f22115d669e24ce990842dab667371b4d > > # bad: [a74d1cafc22e100a9b59c50943ca09c37e03dce8] Merge branches > 'acpi-bus', 'acpi-sleep' and 'acpi-processor' > > git bisect bad a74d1cafc22e100a9b59c50943ca09c37e03dce8 > > # bad: [ce87e09dd88c61f9088768a7708828423549725c] ACPICA: Parser: > > Allow method invocations as target operands git bisect bad > > ce87e09dd88c61f9088768a7708828423549725c > > # good: [0fc5e8f4e4b33ddfa1d1d673fcd420d6e13eb076] ACPICA: Hardware: > > Add sleep register hooks git bisect good > > 0fc5e8f4e4b33ddfa1d1d673fcd420d6e13eb076 > > # good: [a654b8ca6d28736995de767ba62e801fd806a3b2] ACPICA: > > Disassembler: Add Switch/Case disassembly support git bisect good > > a
Re: [Regression Linux 4.11] TPM module not loaded anymore (was: Regression between Linux 3.16 and 4.8/4.9 on Lenovo X60 with coreboot)
On Sun, Apr 09, 2017 at 07:34:43PM +0200, Paul Menzel wrote: > Dear Linux folks, > > > It turns out that stricter checks in the ACPI subsystem, introduced in > commit 57707a9a77 (ACPICA: Resources: Not a valid resource if buffer > length too long) [1], cause the TPM module not to be loaded anymore on > the Lenovo X60 with coreboot [2]. > > Am Freitag, den 07.04.2017, 22:58 +0200 schrieb Paul Menzel: > > On 2017-04-07 22:13, Jarkko Sakkinen wrote: > > > On Thu, Apr 06, 2017 at 01:10:13PM -0600, Jason Gunthorpe wrote: > > >> On Thu, Apr 06, 2017 at 08:26:22PM +0200, Paul Menzel wrote: > > >> > >We added direct ACPI binding to the driver in addition to PNP, so if > > >> > >you have an ACPI table it goes down that path and does some additional > > >> > >validation of what is in the TPM. The BIOS must provide a > > >> > >acpi_dev_resource_memory and a ACPI_SIG_TPM2 for the ACPI entry at a > > >> > >minimum. > > >> > > > >> > Is it correct, that this is added in/for 4.11, so just recently? > > >> > Testing > > >> > with Linux 4.10.8, everything is detected just fine. > > >> > > >> No, it is quite a bit older.. And it should only go for TPM2, which I > > >> don't think you have?? > > >> > > >> Maybe Jarkko has a guess, but sure sounds like something is recently > > >> broken in 4.11 > > > > > > I'll come back to this. I have to re-read the whole mail thread to > > > get back into the context. Lots of multitasking because of release > > > and so forth. Sorry for the latency! > > > > I started bisecting this issue. This is the current state. > > […] > > Here are the results. > > ``` > git bisect log > # bad: [7a771ceac771d009f7203c40b256b0608d7ea2f8] Merge tag 'dm-4.11-changes' > of git://git.kernel.org/pub/scm/linux/kernel/git/device-mapper/linux-dm > # good: [c470abd4fde40ea6a0846a2beab642a578c0b8cd] Linux 4.10 > git bisect start 'HEAD' 'v4.10' > # good: [b3de5ad688f0f52457e73767f95a640ab4158d0d] Merge tag 'regmap-v4.11' > of git://git.kernel.org/pub/scm/linux/kernel/git/broonie/regmap > git bisect good b3de5ad688f0f52457e73767f95a640ab4158d0d > # bad: [fd4a61e08aa79f2b7835b25c6f94f27bd2d65990] sched/core: Fix build > paravirt build on arm and arm64 > git bisect bad fd4a61e08aa79f2b7835b25c6f94f27bd2d65990 > # good: [7aa7d608112baf63a0b1278955f9619427373807] Merge tag 'leds_for_4.11' > of git://git.kernel.org/pub/scm/linux/kernel/git/j.anaszewski/linux-leds > git bisect good 7aa7d608112baf63a0b1278955f9619427373807 > # good: [02c3de1105228e367320e7fdeffbf511904f398c] Merge tag 'pm-4.11-rc1' of > git://git.kernel.org/pub/scm/linux/kernel/git/rafael/linux-pm > git bisect good 02c3de1105228e367320e7fdeffbf511904f398c > # bad: [6c24337f22115d669e24ce990842dab667371b4d] Merge tag > 'fscrypt-for-linus' of > git://git.kernel.org/pub/scm/linux/kernel/git/tytso/fscrypt > git bisect bad 6c24337f22115d669e24ce990842dab667371b4d > # bad: [a74d1cafc22e100a9b59c50943ca09c37e03dce8] Merge branches 'acpi-bus', > 'acpi-sleep' and 'acpi-processor' > git bisect bad a74d1cafc22e100a9b59c50943ca09c37e03dce8 > # bad: [ce87e09dd88c61f9088768a7708828423549725c] ACPICA: Parser: Allow > method invocations as target operands > git bisect bad ce87e09dd88c61f9088768a7708828423549725c > # good: [0fc5e8f4e4b33ddfa1d1d673fcd420d6e13eb076] ACPICA: Hardware: Add > sleep register hooks > git bisect good 0fc5e8f4e4b33ddfa1d1d673fcd420d6e13eb076 > # good: [a654b8ca6d28736995de767ba62e801fd806a3b2] ACPICA: Disassembler: Add > Switch/Case disassembly support > git bisect good a654b8ca6d28736995de767ba62e801fd806a3b2 > # bad: [57707a9a7780fab426b8ae9b4c7b65b912a748b3] ACPICA: Resources: Not a > valid resource if buffer length too long > git bisect bad 57707a9a7780fab426b8ae9b4c7b65b912a748b3 > # good: [7225d0467c59e55566df396d6ecd5baf26ef3d9b] ACPICA: Utilities: Update > debug output > git bisect good 7225d0467c59e55566df396d6ecd5baf26ef3d9b > # first bad commit: [57707a9a7780fab426b8ae9b4c7b65b912a748b3] ACPICA: > Resources: Not a valid resource if buffer length too long > ``` > > I suggest, that just a warning is printed in this case, or that an > option is added to enable some kind of “strict mode” or a quirk table. > > Please find the decompiled DSDT attached. The code to generate the ASL > coreboot code is available [3]. > > Please tell me, what information you need. > > > Kind regards, > > Paul > > > [1] > https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=57707a9a778 > [2] https://review.coreboot.org/13410/ > [3] > https://review.coreboot.org/cgit/coreboot.git/tree/src/drivers/pc80/tpm/tpm.c Hi, Thank you for bisecting the issue. It would have been hard to achieve this without the hardware. Do you want to create a patch for ACPICA? /Jarkko
Re: Linux 4.11: Reported regressions as of Sunday, 2017-04-09
On Sun, Apr 09, 2017 at 07:15:49PM +0200, Thorsten Leemhuis wrote: > Desc: i915 gpu hangs under load > Repo: 2017-03-22 > https://www.mail-archive.com/[email protected]/msg116227.html > https://bugs.freedesktop.org/show_bug.cgi?id=100181 > https://www.mail-archive.com/[email protected]/msg1372182.html > Stat: 2017-04-07 > https://www.mail-archive.com/[email protected]/msg1372182.html > Note: A few patches from Andrea (who's seeing problems as well) are being > discussed Note, Andrea saw a completely different problem unrelated to the GPU hang and date back to ~4.9. Both reported issues have been fixed, with the earlier report already in mainline but Andrea's fix is not yet in a PR. -Chris -- Chris Wilson, Intel Open Source Technology Centre
Linux 4.11: Reported regressions as of Sunday, 2017-04-09
Hi! Find below my third regression report for Linux 4.11. It lists 15 regressions I'm currently aware of. 5 regressions mentioned in last weeks report got fixed. As always: Are you aware of any other regressions? Then please let me know (simply CC [email protected]). And please tell me if there is anything in the report that shouldn't be there. Ciao, Thorsten P.S.: Thx to all those that CCed me on regression reports or provided other input, as that makes compiling these reports a whole lot easier! == Current regressions == Desc: Problems since 5b52330bbfe6 "audit: fix auditd/kernel connection state tracking" Repo: 2017-04-09 https://www.mail-archive.com/[email protected]/msg1373243.html Stat: 2017-04-09 https://www.mail-archive.com/[email protected]/msg1373315.html Note: solution discussed Desc: "Synaptics Touch Digitizer V04" no longer working Repo: 2017-04-08 https://bugzilla.kernel.org/show_bug.cgi?id=195287 Stat: n/a Note: brand new Desc: crash since 617f01211baf ("8139too: use napi_complete_done()") Repo: 2017-04-07 https://www.mail-archive.com/[email protected]/msg162162.html Stat: 2017-04-08 https://www.mail-archive.com/[email protected]/msg162285.html Note: quite new, people are looking into it Desc: Warning since RC4: sed_opal:OPAL: Error on step function: 0 with error -95: Unknown Error Repo: 2017-04-07 https://bugzilla.kernel.org/show_bug.cgi?id=195277 Stat: 2017-04-07 https://bugzilla.kernel.org/show_bug.cgi?id=195277#c1 Note: patch submitted Desc: networking/softirq performance regression due to a part of 374ad05ab64d Repo: 2017-03-29 https://lkml.org/lkml/2017/3/29/758 Stat: 2017-04-05 https://lkml.org/lkml/2017/4/5/553 Note: might be stalled Desc: 4.11 PowerMac G5 970MP: [drm:.r600_ring_test [radeon]] *ERROR* radeon: ring 0 test failed (scratch(0x8504)=0xCAFEDEAD Repo: 2017-03-24 https://bugs.freedesktop.org/show_bug.cgi?id=99851#c26 Stat: n/a Note: looks like reporter (who does not see the problem in 4.10) could need some help bisecting Desc: Commit d8514d8edb5b ("ovl: copy up regular file using O_TMPFILE") breaks ubifs Repo: 2017-03-28 https://www.mail-archive.com/[email protected]/msg1363879.html Stat: 2017-03-30 https://www.mail-archive.com/[email protected]/msg1366190.html https://www.mail-archive.com/[email protected]/msg1366208.html Note: looks stalled after patches to fix issue seemed to do well in tests Desc: 07ec51480b5e ("virtio_pci: use shared interrupts for virtqueues") causes some kworker grief in -rt too Repo: 2017-03-27 https://www.mail-archive.com/search?l=mid&[email protected] Stat: 2017-04-07 https://www.mail-archive.com/[email protected]/msg1372848.html Note: WIP Desc: pine64 defconfig: WARNING: CPU: 0 PID: 86 at drivers/base/dd.c:349 driver_probe_device+0x258/0x2c0 Repo: 2017-03-25 https://bugzilla.kernel.org/show_bug.cgi?id=195037 https://www.mail-archive.com/[email protected]/msg1368488.html Stat: 2017-03-28 https://bugzilla.kernel.org/show_bug.cgi?id=195037#c2 Note: André doesnt have a clue and needs someone with insights devm and devres Desc: NVMe APST? Samsung PM951 NVMe sudden controller death Repo: 2017-03-25 https://bugzilla.kernel.org/show_bug.cgi?id=195039 Stat: 2017-03-29 Note: Poked luto, as it looked stalled; maybe a blacklist update is needed; issue might be related to https://bugzilla.kernel.org/show_bug.cgi?id=194921 (see below) Desc: NVMe APST? NVMe resets leads to capacity change to 0, leading to panics; Samsung SSD as well Repo: 2017-03-18 https://bugzilla.kernel.org/show_bug.cgi?id=194921 Stat: 2017-03-28 Note: Poked luto, as it looked stalled; maybe a blacklist update is needed; issue might be related to https://bugzilla.kernel.org/show_bug.cgi?id=195039 (see above) Desc: Perf regression after enabling nvme APST Repo: 2017-03-17 https://lkml.org/lkml/2017/3/17/177 Stat: 2017-03-20 https://lkml.org/lkml/2017/3/20/998 Note: stalled Desc: i915 gpu hangs under load Repo: 2017-03-22 https://www.mail-archive.com/[email protected]/msg116227.html https://bugs.freedesktop.org/show_bug.cgi?id=100181 https://www.mail-archive.com/[email protected]/msg1372182.html Stat: 2017-04-07 https://www.mail-archive.com/[email protected]/msg1372182.html Note: A few patches from Andrea (who's seeing problems as well) are being discussed Desc: Synaptics RMI4 touchpad regression in 4.11-rc1: pointer jumps Repo: 2017-03-11 https://www.mail-archive.com/[email protected]/msg1351561.html Stat: 2017-03-31 https://www.mail-archive.com/search?l=mid&[email protected] Note: stalled; two patched to improve the situation available; Desc: Synaptics RMI4 touchpad regression in 4.11-rc1: palm detection Repo: 2017-03-11 https://www.mail-archive.com/[email protected]/ms
Linux 4.11-rc6
o-maintainer of PHYLIB Florian Westphal (1): secure_seq: downgrade to per-host timestamp offsets Frederic Barrat (1): powerpc/mm: Add missing global TLB invalidate if cxl is active Gao Feng (1): netfilter: nf_nat_snmp: Fix panic when snmp_trap_helper fails to register Gleb Fotengauer-Malinovskiy (1): jump label: fix passing kbuild_cflags when checking for asm goto support Grygorii Strashko (1): net: ethernet: ti: cpsw: wake tx queues on ndo_tx_timeout Guenter Roeck (1): sparc32: Export vac_cache_size to fix build error Guillaume Nault (9): l2tp: hold tunnel socket when handling control frames in l2tp_ip and l2tp_ip6 l2tp: purge socket queues in the .destruct() callback l2tp: fix race in l2tp_recv_common() l2tp: ensure session can't get removed during pppol2tp_session_ioctl() l2tp: fix duplicate session creation l2tp: hold session while sending creation notifications l2tp: take a reference on sessions used in genetlink handlers l2tp: take reference on sessions being dumped l2tp: fix PPP pseudo-wire auto-loading Hans de Goede (1): gpio: acpi: Call enable_irq_wake for _IAE GpioInts with Wake set Harald Freudenberger (1): s390/pkey: Fix wrong handling of secure key with old MKVP Hauke Mehrtens (1): MIPS: Lantiq: fix missing xbar kernel panic Heiko Carstens (3): s390/smp: fix ipl from cpu with non-zero address s390/uaccess: get_user() should zero on failure (again) KVM: s390: remove change-recording override support Huacai Chen (4): MIPS: Add MIPS_CPU_FTLB for Loongson-3A R2 MIPS: Check TLB before handle_ri_rdhwr() for Loongson-3 MIPS: Flush wrong invalid FTLB entry for huge page MIPS: c-r4k: Fix Loongson-3's vcache/scache waysize calculation Hugh Dickins (1): mm: fix page_vma_mapped_walk() for ksm pages Jakub Kicinski (1): nfp: fix potential use after free on xdp prog James Hogan (10): MIPS: Force o32 fp64 support on 32bit MIPS64r6 kernels MIPS: Include asm/ptrace.h now linux/sched.h doesn't MIPS: Wire up statx system call metag/usercopy: Drop unused macros metag/usercopy: Fix alignment error checking metag/usercopy: Add early abort to copy_to_user metag/usercopy: Zero rest of buffer from copy_from_user metag/usercopy: Set flags before ADDZ metag/usercopy: Fix src fixup in from user rapf loops metag/usercopy: Add missing fixups Jan Beulich (1): xenbus: remove transaction holder from list before freeing Jan-Marek Glogowski (1): Reset TreeId to zero on SMB2 TREE_CONNECT Jarno Rajahalme (1): openvswitch: Fix refcount leak on force commit. Jeff Kirsher (1): Revert "e1000e: driver trying to free already-free irq" Jeffy Chen (2): netfilter: nfnl_cthelper: Fix memory leak mailmap: update Yakir Yang email address Jessica Yu (1): vmlinux.lds: add missing VMLINUX_SYMBOL macros Joe Thornber (1): dm cache metadata: fix metadata2 format's blocks_are_clean_separate_dirty Johan Hovold (1): Documentation: stable-kernel-rules: fix stable-tag format Johannes Berg (1): mac80211: unconditionally start new netdev queues with iTXQ support John Crispin (1): MIPS: ralink: Fix typos in rt3883 pinctrl Jon Medhurst (1): arm: kprobes: Align stack to 8-bytes in test code Jonas Jensen (1): net: moxa: fix TX overrun memory leak Jordan Crouse (3): drm/msm: Fix wrong pointer check in a5xx_destroy drm/msm: Don't allow zero sized buffer objects drm/msm: Make sure to detach the MMU during GPU cleanup Julian Wiedmann (2): s390/qeth: size calculation outbound buffers s390/qeth: no ETH header for outbound AF_IUCV Ladi Prosek (2): KVM: nVMX: do not leak PML full vmexit to L1 KVM: nVMX: initialize PML fields in vmcs02 Larry Finger (1): rtlwifi: Fix scheduling while atomic splat Li Qiang (1): drm/vmwgfx: fix integer overflow in vmw_surface_define_ioctl() Liad Kaufman (1): iwlwifi: mvm: support ibss in dqa mode Linus Torvalds (1): Linux 4.11-rc6 Liping Zhang (8): netfilter: nfnl_cthelper: fix incorrect helper->expect_class_max netfilter: invoke synchronize_rcu after set the _hook_ to NULL netfilter: nfnl_cthelper: fix a race when walk the nf_ct_helper_hash table netfilter: nf_ct_ext: fix possible panic after nf_ct_extend_unregister netfilter: nfnetlink_queue: fix secctx memory leak sysctl: add sanity check for proc_douintvec sysctl: don't print negative flag for proc_douintvec sysctl: report EINVAL if value is larger than UINT_MAX for proc_douintvec Marc Zyngier (2): arm/arm64: KVM: Take mmap_sem in stage2_unmap_vm arm/arm64: KVM: Take mmap_sem in kvm_arch_prepare_memory_region Marcelo Henrique Cerri (1): s390/decompressor: fix initrd corruption caused by
Re: Linux 4.11: Reported regressions as of Tuesday, 2017-04-02
On 02/04/17 10:03 PM, Thorsten Leemhuis wrote: > > == Going to be removed from the list == > > [...] > > Desc: DRM BUG while initializing cape verde (2nd card) > Repo: 2017-03-13 https://bugzilla.kernel.org/show_bug.cgi?id=194867 > Stat: n/a > Note: problem was in 4.10 already & reporter closed issue There are two separate issues discussed in this bug report. The first one (described in the bug title and initial description) was a regression and fixed by Alex's patches. The other issue (described in comment 3) is not a regression, I asked Janpieter to file a separate report for that. -- Earthling Michel Dänzer | http://www.amd.com Libre software enthusiast | Mesa and X developer
Linux 4.11-rc5
try Vyukov (1): kvm: fix usage of uninit spinlock in avic_vm_destroy() Eric Anholt (1): drm/vc4: Allocate the right amount of space for boot-time CRTC state. Eric Biggers (1): crypto: xts,lrw - fix out-of-bounds write after kmalloc failure Gary R Hook (1): crypto: ccp - Make some CCP DMA channels private Geert Uytterhoeven (3): m68k/bitops: Correct signature of test_bit() m68k/defconfig: Update defconfigs for v4.11-rc1 m68k: Wire up statx Goldwyn Rodrigues (1): btrfs: Change qgroup_meta_rsv to 64bit Hans de Goede (1): mmc: sdhci: Disable runtime pm when the sdio_irq is enabled Helge Deller (3): parisc: Fix access fault handling in pa_memcpy() parisc: Clean up fixup routines for get_user()/put_user() parisc: Avoid stalled CPU warnings after system shutdown Herongguang (Stephen) (1): KVM: pci-assign: do not map smm memory slot pages in vt-d page tables Hiroyuki Yokoyama (1): ASoC: rsnd: fix sound route path when using SRC6/SRC9 Hui Wang (1): ALSA: hda - fix a problem for lineout on a Dell AIO machine Ingo Molnar (1): sched/headers: Remove duplicate #include line Jaehoon Chung (1): scsi: ufs: remove the duplicated checking for supporting clkscaling James Morse (1): ACPI / APEI: Add missing synchronize_rcu() on NOTIFY_SCI removal Jason A. Donenfeld (1): padata: avoid race in reordering Jason Wang (1): virtio_pci: fix out of bound access for msix_names Javier Martinez Canillas (1): usb: phy: isp1301: Fix build warning when CONFIG_OF is disabled Jeeja KP (2): ASoC: hdac_hdmi: avoid reference to invalid variable of the pin list ASoC: hdac_hdmi: don't update the iterator in pcm list remove Jens Axboe (1): blk-mq: include errors in did_work calculation Jim Mattson (1): kvm: vmx: Flush TLB when the APIC-access address changes Joerg Roedel (2): ACPI: ioapic: Clear on-stack resource before using it ACPI: Do not create a platform_device for IOAPIC/IOxAPIC Johannes Weiner (2): mm: rmap: fix huge file mmap accounting in the memcg stats mm: workingset: fix premature shadow node shrinking with cgroups John Garry (1): scsi: libsas: fix ata xfer length Josef Bacik (3): nbd: handle ERESTARTSYS properly nbd: set rq->errors to actual error code nbd: set queue timeout properly Josh Poimboeuf (2): ACPI: Fix incompatibility with mcount-based function graph tracing x86/build: Mostly disable '-maccumulate-outgoing-args' Jérémy Lefaure (1): EDAC, i5000, i5400: Fix use of MTR_DRAM_WIDTH macro Kees Cook (2): lib/syscall: Clear return values when no stack mm: fix section name for .data..ro_after_init Kinglong Mee (2): SUNRPC/backchanel: set XPT_CONG_CTRL flag for bc xprt nfsd: map the ENOKEY to nfserr_perm for avoiding warning Kuninori Morimoto (3): ASoC: rcar: avoid SSI_MODEx settings for SSI8 ASoC: rcar: clear DE bit only in PDMACHCR when it stops ASoC: rcar: dma: remove unnecessary "volatile" Ladi Prosek (3): KVM: nVMX: fix nested EPT detection virtio_balloon: init 1st buffer in stats vq virtio-balloon: use actual number of stats for stats queue buffers Linus Torvalds (1): Linux 4.11-rc5 Liu Bo (1): Btrfs: bring back repair during read Lucas Stach (2): ASoC: simple-card: fix simple_dai clk lookup drm/etnaviv: (re-)protect fence allocation with GPU mutex Ludovic Desroches (1): mmc: sdhci-of-at91: fix MMC_DDR_52 timing selection Luiz Capitulino (1): KVM: Documentation: document MCE ioctls Manish Rangankar (1): scsi: qedi: Add PCI device-ID for QL41xxx adapters. Mark Rutland (1): kasan: report only the first error by default Mark Salter (1): arm64: fix NULL dereference in have_cpu_die() Masahiro Yamada (1): arm64: drop non-existing vdso-offsets.h from .gitignore Mathias Nyman (2): xhci: Set URB actual length for stopped control transfers xhci: Manually give back cancelled URB if we can't queue it for cancel Matt Redfearn (1): irqchip/mips-gic: Fix Local compare interrupt Matthew Wilcox (1): thermal: Fix potential deadlock in cpu_cooling Matthias Kaehlcke (1): dmaengine: Fix array index out of bounds warning in __get_unmap_pool() Matthias Reichl (1): dmaengine: bcm2835: Fix cyclic DMA period splitting Michal Hocko (1): mm: move mm_percpu_wq initialization earlier Michel Dänzer (1): drm/radeon: Override fpfn for all VRAM placements in radeon_evict_flags Mike Galbraith (1): kasan: do not sanitize kexec purgatory Mike Kravetz (2): hugetlbfs: initialize shared policy as part of inode allocation mm/hugetlb.c: don't call region_abort if region_chg fails Mike Looijmans (1): i2c: mux: pca954x: Add missing pca9546 definition to chip_desc Mike Travis (1):
Linux 4.11: Reported regressions as of Tuesday, 2017-04-02
Hi! Find below my second regression report for Linux 4.11. It lists 13 regressions I'm currently aware of. It lists 6 fixed regressions. Some of them where in the first report from three weeks ago; a few were supposed to go into a second report I prepared last week, but wasn't able to finish :-/ As always: Are you aware of any other regressions? Then please let me know (simply CC [email protected]). And please tell me if there is anything in the report that shouldn't be there. Ciao, Thorsten P.S.: Thx to all those that CCed me on regression reports, that makes compiling these reports a whole lot easier! == Current regressions == Desc: malta_defconfig regressions Repo: 2017-03-31 https://www.mail-archive.com/[email protected]/msg1367470.html Stat: n/a Note: some patched already heading mainline Desc: Commit d8514d8edb5b ("ovl: copy up regular file using O_TMPFILE") breaks ubifs Repo: 2017-03-28 https://www.mail-archive.com/[email protected]/msg1363879.html Stat: 2017-03-30 https://www.mail-archive.com/[email protected]/msg1366190.html https://www.mail-archive.com/[email protected]/msg1366208.html Note: patches being tested; tests looking good so far Desc: 07ec51480b5e ("virtio_pci: use shared interrupts for virtqueues") causes some kworker grief in -rt too Repo: 2017-03-27 https://www.mail-archive.com/search?l=mid&[email protected] Stat: 2017-03-31 https://www.mail-archive.com/search?l=mid&[email protected] Note: hch is looking into this Desc: HP 820 G3 becomes unstable after resume from suspend Repo: 2017-03-25 https://bugzilla.kernel.org/show_bug.cgi?id=195041 Stat: 2017-03-26 Note: might be a duplicate of https://bugzilla.kernel.org/show_bug.cgi?id=194801 ; revert for that bug is heading upstream via davem (see https://www.mail-archive.com/[email protected]/msg1361534.html ) Desc: NVMe APST? Samsung PM951 NVMe sudden controller death Repo: 2017-03-25 https://bugzilla.kernel.org/show_bug.cgi?id=195039 Stat: 2017-03-29 Note: Got luto and axboe into the loop, investigation ongoing, maybe a blacklist update is needed; issue might be the same to https://bugzilla.kernel.org/show_bug.cgi?id=194921 (see below) Desc: NVMe APST? NVMe resets leads to capacity change to 0, leading to panics; Samsung SSD as well Repo: 2017-03-18 https://bugzilla.kernel.org/show_bug.cgi?id=194921 Stat: 2017-03-28 Note: Got luto and axboe into the loop, investigation ongoing; maybe a blacklist update is needed; issue might be related to https://bugzilla.kernel.org/show_bug.cgi?id=195039 (see above) Desc: Perf regression after enabling nvme APST Repo: 2017-03-17 https://lkml.org/lkml/2017/3/17/177 Stat: 2017-03-20 https://lkml.org/lkml/2017/3/20/998 Note: luto: lying disk? Desc: i915 gpu hangs under load Repo: 2017-03-22 https://www.mail-archive.com/[email protected]/msg116227.html https://bugs.freedesktop.org/show_bug.cgi?id=100181 Stat: 2017-04-02 https://www.mail-archive.com/[email protected]/msg117315.html Note: Reporter: "there's a fix out there. I don't know if it's in rc5 though." Desc: 4.10/4.11: mmc: core: HS DDR switch, don't change timing before checking status, as it might lead to boot problems Repo: 2017-03-10 https://patchwork.kernel.org/patch/9617489/ Stat: 2017-03-24 Note: looks like the real root cause was found, but then the discussion stalled afaics Desc: Synaptics RMI4 touchpad regression in 4.11-rc1: pointer jumps Repo: 2017-03-11 https://www.mail-archive.com/[email protected]/msg1351561.html Stat: 2017-03-31 https://www.mail-archive.com/search?l=mid&[email protected] Note: two patches to improve the situation available; discussion which to use Desc: Synaptics RMI4 touchpad regression in 4.11-rc1: palm detection Repo: 2017-03-11 https://www.mail-archive.com/[email protected]/msg1351561.html Stat: 2017-03-19 https://www.mail-archive.com/[email protected]/msg1356832.html Note: discussion stalled; asked for an update Desc: e1000e: __pci_enable_msi_range fails before/after resume Repo: 2017-03-06 https://bugzilla.kernel.org/show_bug.cgi?id=194801 Stat: 2017-03-14 https://bugzilla.kernel.org/show_bug.cgi?id=194801#c1 Note: revert for that bug is heading upstream via davem (see https://www.mail-archive.com/[email protected]/msg1361534.html ) Desc: thinkpad x220: GPU hang Repo: 2017-03-05 https://www.mail-archive.com/[email protected]/msg1345689.html Stat: 2017-03-25 https://www.mail-archive.com/[email protected]/msg180860.html Note: Ignored by DRI people? Pavel wrote: "We know where the bug is, but there's no fix for it. There was one patch, but it was quickly withdrawn." == Stalled, waiting for feedback from reporter == Desc: pine64 defconfig: WARNING: CPU
Linux 4.11-rc4
ck between crypto_alg_sem/rtnl_mutex/genl_mutex
Huang Rui (1):
drm/amdgpu: fix the clearing wb size
Huang Ying (1):
mm, swap: Remove WARN_ON_ONCE() in free_swap_slot()
Hui Wang (1):
ALSA: hda - Adding a group of pin definition to fix headset problem
Icenowy Zheng (2):
ARM: sun8i: a23/a33: drop bl_en_pin GPIO pinmux in reference design DTSI
clk: sunxi-ng: fix recalc_rate formula of NKMP clocks
Ilya Dryomov (1):
libceph: force GFP_NOIO for socket allocations
Jack Morgenstein (1):
net/mlx4_core: Avoid delays during VF driver device shutdown
Jaegeuk Kim (3):
f2fs: don't overwrite node block by SSR
f2fs: declare static functions
f2fs: use __set{__clear}_bit_le
Jaehoon Chung (1):
phy: phy-exynos-pcie: fix the wrong error return
James Hogan (1):
serial: 8250_dw: Fix breakage when HAVE_CLK=n
James Smart (1):
scsi: lpfc: Finalize Kconfig options for nvme
Janusz Dziedzic (1):
usb: dwc3: gadget: delay unmap of bounced requests
Jaroslav Kysela (2):
ALSA: hda - add support for docking station for HP 820 G2
ALSA: hda - add support for docking station for HP 840 G3
Jason Gunthorpe (1):
infiniband: Fix alignment of mmap cookies to support VIPT caching
Johan Hovold (16):
USB: idmouse: fix NULL-deref at probe
USB: lvtest: fix NULL-deref at probe
USB: uss720: fix NULL-deref at probe
USB: wusbcore: fix NULL-deref at probe
uwb: hwa-rc: fix NULL-deref at probe
uwb: i1480-dfu: fix NULL-deref at probe
mmc: ushc: fix NULL-deref at probe
Input: iforce - validate number of endpoints before using them
Input: cm109 - validate number of endpoints before using them
Input: ims-pcu - validate number of endpoints before using them
Input: yealink - validate number of endpoints before using them
Input: hanwang - validate number of endpoints before using them
Input: kbtab - validate number of endpoints before using them
Input: sur40 - validate number of endpoints before using them
USB: usbtmc: add missing endpoint sanity check
USB: usbtmc: fix probe error path
Johannes Berg (1):
nl80211: fix dumpit error path RTNL deadlocks
Jon Mason (5):
ARM: dts: BCM5301X: Fix UARTs on bcm953012k
ARM: dts: BCM5301X: Fix memory start address
ARM: dts: BCM5301X: Correct GIC_PPI interrupt flags
ARM: dts: NSP: GPIO reboot open-source
arm64: dts: NS2: Add dma-coherent to relevant DT entries
K. Y. Srinivasan (2):
Drivers: hv: vmbus: Don't leak channel ids
Drivers: hv: vmbus: Don't leak memory when a channel is rescinded
Kai-Heng Feng (1):
Input: i8042 - add noloop quirk for Dell Embedded Box PC 3000
Kenneth Graunke (1):
drm/i915: Drop support for I915_EXEC_CONSTANTS_* execbuf parameters.
Koos Vriezen (1):
iommu/vt-d: Fix NULL pointer dereference in device_to_iommu
Kris Murphy (1):
openvswitch: Add missing case OVS_TUNNEL_KEY_ATTR_PAD
Krzysztof Kozlowski (2):
drm/exynos: Remove support for Exynos4415 (SoC not supported anymore)
drm/exynos: Print kernel pointers in a restricted form
Krzysztof Opasiak (1):
usb: gadget: f_hid: fix: Don't access hidg->req without spinlock held
Ladislav Michl (2):
ARM: OMAP2+: gpmc-onenand: propagate error on initialization failure
ARM: OMAP2+: Remove legacy gpmc-nand.c
Lars-Peter Clausen (1):
iio: sw-device: Fix config group initialization
Lee Jones (1):
serial: st-asc: Use new GPIOD API to obtain RTS pin
Lendacky, Thomas (2):
amd-xgbe: Fix jumbo MTU processing on newer hardware
amd-xgbe: Fix the ECC-related bit position definitions
Leon Romanovsky (1):
IB/rxe: Update documentation link
Leonard Crestez (1):
clk: core: Copy connection id
Linus Torvalds (1):
Linux 4.11-rc4
Linus Walleij (1):
ARM: dts: add the AB8500 clocks to the device tree
Liping Zhang (3):
netfilter: nft_set_bitmap: fetch the element key based on the set->klen
netfilter: nf_tables: fix mismatch in big-endian system
netfilter: nft_ct: do cleanup work when NFTA_CT_DIRECTION is invalid
Liu Bo (1):
Btrfs: fix regression in lock_delalloc_pages
Lorenzo Bianconi (1):
iio: imu: st_lsm6dsx: fix FIFO_CTRL2 overwrite during watermark
configuration
Maor Gottlieb (1):
net/mlx5: Increase number of max QPs in default profile
Marek Szyprowski (2):
iommu/exynos: Block SYSMMU while invalidating FLPD cache
iommu/exynos: Workaround FLPD cache flush issues for SYSMMU v5
Masaki Ota (2):
Input: ALPS - fix V8+ protocol handling (73 03 28)
Input: ALPS - fix trackstick button handling on V8 devices
Matjaz Hegedic (1):
Input: elan_i2c - add ASUS EeeBook X205TA special touchpad fw
Matthijs van Duin (1):
ARM: OMAP5 / DRA7: Fix HYP mode boot for thumb2 build
Maxime Ripard (1):
ARM: sun8i: Fix the mali clock rate
Linux 4.11-rc3
(1): arm64: kernel: Update kerneldoc for cpu_suspend() rename Guoqing Jiang (3): md-cluster: free md_cluster_info if node leave cluster md-cluster: remove useless memset from gather_all_resync_info md: move funcs from pers->resize to update_size Gwendal Grignou (1): libata: transport: Remove circular dependency at free time Hannes Frederic Sowa (2): tun: fix premature POLLOUT notification on tun devices dccp: fix memory leak during tear-down of unsuccessful connection request Heiko Carstens (2): mm: add private lock to serialize memory hotplug operations drivers core: remove assert_held_device_hotplug() Helge Deller (3): parisc: Wire up statx system call parisc: Avoid compiler warnings with access_ok() parisc: Fix system shutdown halt Himanshu Madhani (2): qla2xxx: Add DebugFS node to display Port Database qla2xxx: Update driver version to 9.00.00.00-k Huy Nguyen (1): net/mlx5e: remove IEEE/CEE mode check when setting DCBX mode Igor Druzhinin (1): xen-netback: fix race condition on XenBus disconnect Imre Deak (1): drm/i915/gen9: Increase PCODE request timeout to 50ms James Smart (20): scsi: lpfc: remove redundant assignment of sgel scsi: lpfc: sanity check hrq is null before dereferencing it scsi: lpfc: don't dereference dma_buf->iocbq before null check scsi: lpfc: fix missing spin_unlock on sql_list_lock scsi: lpfc: Fix crash during Hardware error recovery on SLI3 adapters scsi: lpfc: Fix RCTL value on NVME LS request and response scsi: lpfc: Fix NVME CMD IU byte swapped word 1 problem scsi: lpfc: Fix IO submission if WQ is full scsi: lpfc: Fix nvme allocation bug on failed nvme_fc_register_localport scsi: lpfc: add NVME exchange aborts scsi: lpfc: Fix eh_deadline setting for sli3 adapters. scsi: lpfc: add transport eh_timed_out reference scsi: lpfc: Rework lpfc Kconfig for NVME options scsi: lpfc: Rename LPFC_MAX_EQ_DELAY to LPFC_MAX_EQ_DELAY_EQID_CNT scsi: lpfc: correct double print scsi: lpfc: remove dead sli3 nvme code scsi: lpfc: correct rdp diag portnames scsi: lpfc: code cleanups in NVME initiator base scsi: lpfc: code cleanups in NVME initiator discovery scsi: lpfc: revise version number to 11.2.0.10 Jarod Wilson (1): team: use ETH_MAX_MTU as max mtu Jason Yan (3): md: fix super_offset endianness in super_1_rdev_size_change md: fix incorrect use of lexx_to_cpu in does_sb_need_changing nfs: make nfs4_cb_sv_ops static Jens Axboe (1): blk-mq-sched: don't run the queue async from blk_mq_try_issue_directly() Jiri Olsa (1): x86/intel_rdt: Put group node in rdtgroup_kn_unlock Jiri Pirko (3): mlxsw: spectrum_flower: Remove bogus warns in mlxsw_sp_flower_destroy mlxsw: reg: Fix SPVM max record count mlxsw: reg: Fix SPVMLR max record count Joe Carnuccio (1): qla2xxx: Allow vref count to timeout on vport delete. Joe Perches (3): scsi: qla2xxx: Fix ql_dump_buffer scsi: qedf: Fix defective logging format and argument mismatches scsi: qedf: Use vsprintf extension %pad Johan Hovold (2): isdn/gigaset: fix NULL-deref at probe net: wimax/i2400m: fix NULL-deref at probe John David Anglin (1): parisc: Optimize flush_kernel_vmap_range and invalidate_kernel_vmap_range Jon Maxwell (1): dccp/tcp: fix routing redirect race Josh Poimboeuf (1): x86/unwind: Fix last frame check for aligned function stacks João Paulo Rechi Vita (2): platform/x86: asus-wmi: Detect quirk_no_rfkill from the DSDT platform/x86: asus-wmi: Remove quirk_no_rfkill Jyri Sarha (2): drm/tilcdc: Fix hardcoded fail-return value in tilcdc_crtc_create() drm/tilcdc: Set framebuffer DMA address to HW only if CRTC is enabled Kees Cook (1): cgroups: censor kernel pointer in debug files Kinglong Mee (3): nfs4: fix a typo of NFS_ATTR_FATTR_GROUP_NAME NFSv4: fix a reference leak caused WARNING messages NFS: fix the fault nrequests decreasing for nfs_inode COPY Kirill A. Shutemov (1): mm, gup: fix typo in gup_p4d_range() Krzysztof Kozlowski (2): crypto: s5p-sss - Fix completing crypto request in IRQ handler crypto: s5p-sss - Fix spinlock recursion on LRW(AES) LABBE Corentin (1): tun: remove copyright printing Larry Finger (1): powerpc/pmac: Fix crash in dma-mapping.h with NULL dma_ops Lendacky, Thomas (1): amd-xgbe: Enable IRQs only if napi_complete_done() is true Linus Torvalds (2): mm/swap: don't BUG_ON() due to uninitialized swap slot cache Linux 4.11-rc3 Maarten Lankhorst (2): drm/i915: Move updating color management to before vblank evasion drm/i915: Nuke skl_update_plane debug message from the pipe update critical section Madhavan Srinivasan (2): powerpc/perf: Fix perf_get_dat
Re: linux-4.11-rc1/drivers/gpu/drm/amd/amdgpu/vi.c: 3 bugs
On Mon, Mar 6, 2017 at 4:40 AM, David Binderman wrote: > > Hello there, > 1 > > [linux-4.11-rc1/drivers/gpu/drm/amd/amdgpu/vi.c:1041] -> > [linux-4.11-rc1/drivers/gpu/drm/amd/amdgpu/vi.c:1037]: (style) Same > expression on both sides of '|'. > > Maybe the macro AMD_CG_SUPPORT_GFX_MGLS is used twice ? > > 2. > > [linux-4.11-rc1/drivers/gpu/drm/amd/amdgpu/vi.c:1070] -> > [linux-4.11-rc1/drivers/gpu/drm/amd/amdgpu/vi.c:1066]: (style) Same > expression on both sides of '|'. > > Duplicate. > > In the same file: > > linux-4.11-rc1/drivers/gpu/drm/amd/amdgpu/vi.c:792]: (style) Variable 'r' is > assigned a value that is never used. > > Source code is > > r = vi_set_uvd_clock(adev, dclk, ixCG_DCLK_CNTL, ixCG_DCLK_STATUS); > > return 0; Thanks, patches sent. Alex > > Regards > > David Binderman > ___ > amd-gfx mailing list > [email protected] > https://lists.freedesktop.org/mailman/listinfo/amd-gfx
Re: Linux 4.11: Reported regressions as of Tuesday, 20176-03-14
[ Moving this sub-thread to the amd-gfx mailing list ] On 14/03/17 07:02 PM, Thorsten Leemhuis wrote: > Hi! Find below my first regression report for Linux 4.11. It lists 9 > regressions I'm currently aware of. [...] > Desc: DRM BUG while initializing cape verde (2nd card) > Repo: 2017-03-13 https://bugzilla.kernel.org/show_bug.cgi?id=194867 > Stat: n/a > Note: patch proposed by reporter I don't see any patch. Looks like the amdgpu driver has never fully initialized GDS support for SI family GPUs, and this now triggers the DRM_MM_BUG_ON which was added to drm_mm_init in 4.11. AMD folks, should this be addressed by fleshing out SI GDS support, or by completely disabling GDS initialization for SI? -- Earthling Michel Dänzer | http://www.amd.com Libre software enthusiast | Mesa and X developer
Re: Linux 4.11: Reported regressions as of Tuesday, 20176-03-14
Thorsten Leemhuis writes: > Hi! Find below my first regression report for Linux 4.11. It lists 9 > regressions I'm currently aware of. > > As always: Are you aware of any other regressions? Then please let me > know (simply CC [email protected]). And please tell me if there > is anything in the report that shouldn't be there. > > Ciao, Thorsten > > P.S.: Sorry, I didn't compile any regression reports for 4.10: I > didn't find time due to various reasons (vacation, a cold, regular > work, and attending two conferences). Reminder: compiling these reports > has nothing to do with my paid job and I'm doing it in my spare time > just because I think someone should do it. > > P.P.S: Dear Gmane mainling list archive webinterface, please come > back soon. I really really miss you. It hurts ever single day. > Don't you miss me, too? ;-) > > == Current regressions == > > Desc: PowerPC crashes on boot, bisected to commit 5657933dbb6e > Repo: 2017-03-02 > https://www.mail-archive.com/[email protected]/msg1343553.html > Stat: 2017-03-09 > https://www.mail-archive.com/[email protected]/msg1349568.html > Note: patch hopefully heading mainline Now fixed in Linus' tree by commit 46f401c4297a. cheers
Re: Linux 4.11: Reported regressions as of Tuesday, 20176-03-14
On Tue, Mar 14, 2017 at 3:02 AM, Thorsten Leemhuis wrote: > > Desc: PowerPC crashes on boot, bisected to commit 5657933dbb6e > Repo: 2017-03-02 > https://www.mail-archive.com/[email protected]/msg1343553.html > Stat: 2017-03-09 > https://www.mail-archive.com/[email protected]/msg1349568.html > Note: patch hopefully heading mainline Should already be mainline as commit 46f401c4297a ("powerpc/pmac: Fix crash in dma-mapping.h with NULL dma_ops") but didn't make rc2. Linus
Linux 4.11: Reported regressions as of Tuesday, 20176-03-14
Hi! Find below my first regression report for Linux 4.11. It lists 9 regressions I'm currently aware of. As always: Are you aware of any other regressions? Then please let me know (simply CC [email protected]). And please tell me if there is anything in the report that shouldn't be there. Ciao, Thorsten P.S.: Sorry, I didn't compile any regression reports for 4.10: I didn't find time due to various reasons (vacation, a cold, regular work, and attending two conferences). Reminder: compiling these reports has nothing to do with my paid job and I'm doing it in my spare time just because I think someone should do it. P.P.S: Dear Gmane mainling list archive webinterface, please come back soon. I really really miss you. It hurts ever single day. Don't you miss me, too? ;-) == Current regressions == Desc: PowerPC crashes on boot, bisected to commit 5657933dbb6e Repo: 2017-03-02 https://www.mail-archive.com/[email protected]/msg1343553.html Stat: 2017-03-09 https://www.mail-archive.com/[email protected]/msg1349568.html Note: patch hopefully heading mainline Desc: thinkpad x220: GPU hang Repo: 2017-03-05 https://www.mail-archive.com/[email protected]/msg1345689.html Stat: n/a Note: poked discussion for a status update Desc: e1000e: __pci_enable_msi_range fails before/after resume Repo: 2017-03-06 https://bugzilla.kernel.org/show_bug.cgi?id=194801 Stat: 2017-03-06 https://bugzilla.kernel.org/show_bug.cgi?id=194801#c1 Note: poked bug for status; might need to get forwared to network people Desc: Two batteries is detected on DEXP Ursus 7W tablet instead of one Repo: 2017-03-07 https://bugzilla.kernel.org/show_bug.cgi?id=194811 Stat: 2017-03-12 https://bugzilla.kernel.org/show_bug.cgi?id=194811#c8 Note: patch likely heading mainline Desc: [lkp-robot] [f2fs] 4ac912427c: -33.7% aim7.jobs-per-min regression Repo: 2017-03-08 https://www.spinics.net/lists/kernel/msg2459239.html Stat: 2017-03-13 https://www.mail-archive.com/[email protected]/msg1353085.html Note: patch discussed and heading mainline Desc: VM with virtio-scsi drive often crashes during boot with kernel 4.11rc1 Repo: 2017-03-09 https://bugzilla.kernel.org/show_bug.cgi?id=194837 Stat: n/a Note: will forward this to scsi & virtio & kvm people Desc: general protection fault: inet6_fill_ifaddr+0x6c/0x230 Repo: 2017-03-11 https://bugzilla.kernel.org/show_bug.cgi?id=194849 Stat: n/a Note: poked bug for status; might need to get forwared to network people Desc: Synaptics RMI4 touchpad regression in 4.11-rc1 Repo: 2017-03-11 https://www.mail-archive.com/[email protected]/msg1351561.html Stat: 2017-03-13 https://www.mail-archive.com/[email protected]/msg1352399.html Note: solution discussed, no patch yet Desc: DRM BUG while initializing cape verde (2nd card) Repo: 2017-03-13 https://bugzilla.kernel.org/show_bug.cgi?id=194867 Stat: n/a Note: patch proposed by reporter
Re: Linux 4.11-rc2
On Mon, Mar 13, 2017 at 09:15:21AM -0700, Linus Torvalds wrote: On Mon, Mar 13, 2017 at 9:05 AM, Josh Boyer wrote: Yes. A git pull just grabbed it for me. The 'view diff' link on kernel.org still fails with bad object, but I'm guessing that will catch up at some point too. Hmm. I pushed those before the announcement, so over 18 hours ago by now. If there still is something that hasn't mirrored out, that implies some problem rather than just a delay. I don't see anything odd when I go to git.kernel.org, but the outward-facing public mirrors are all geolocated, and some of that infrastructure is new. So there might be stale DNS information, or somethign else going on. Adding Konstantin to the bcc to notify him. Konstantin: it apparently took a long time for the 4.11-rc2 tag to mirror out, and there's still some missing object going on.. I'm not sure where Josh is geographically, which might matter for the new GeoDNS. Yes, the EWR mirror was Not Doing The Right Thing, and has been given a stern talking-to (about an hour ago). Sorry about that. -K
Re: Linux 4.11-rc2
On Mon, Mar 13, 2017 at 9:05 AM, Josh Boyer wrote: > > Yes. A git pull just grabbed it for me. The 'view diff' link on > kernel.org still fails with bad object, but I'm guessing that will > catch up at some point too. Hmm. I pushed those before the announcement, so over 18 hours ago by now. If there still is something that hasn't mirrored out, that implies some problem rather than just a delay. I don't see anything odd when I go to git.kernel.org, but the outward-facing public mirrors are all geolocated, and some of that infrastructure is new. So there might be stale DNS information, or somethign else going on. Adding Konstantin to the bcc to notify him. Konstantin: it apparently took a long time for the 4.11-rc2 tag to mirror out, and there's still some missing object going on.. I'm not sure where Josh is geographically, which might matter for the new GeoDNS. Linus
Re: Linux 4.11-rc2
On Mon, Mar 13, 2017 at 11:57 AM, Linus Torvalds wrote: > On Mon, Mar 13, 2017 at 6:19 AM, Josh Boyer wrote: >> >> I thought it might just be me, but at least one other person doesn't >> see the v4.11-rc2 tag in git yet. The patch is on kernel.org though, >> so it's confusing. Did you forget to push it out? > > It's definitely there, but it might have taken a while to mirror out > to all the public mirrors. I'm assuming you see it now? Yes. A git pull just grabbed it for me. The 'view diff' link on kernel.org still fails with bad object, but I'm guessing that will catch up at some point too. Thanks. josh
Re: Linux 4.11-rc2
On Mon, Mar 13, 2017 at 6:19 AM, Josh Boyer wrote: > > I thought it might just be me, but at least one other person doesn't > see the v4.11-rc2 tag in git yet. The patch is on kernel.org though, > so it's confusing. Did you forget to push it out? It's definitely there, but it might have taken a while to mirror out to all the public mirrors. I'm assuming you see it now? Linus
Re: Linux 4.11-rc2
On Sun, Mar 12, 2017 at 6:01 PM, Linus Torvalds wrote: > As usual, the week after rc1 tends to be fairly quiet when people are > still looking for bugs and taking a breather after the merge window. > But we've got a healthy number of fixes in, and there's some > cleanup/prep patches for the upcoming 5-level page table support that > I took after the merge window just to make the next merge window > easier. > > There's also a (small) late random driver update. > > But most of it is just fixes, with arch and drivers being the bulk of > it (powerpc and i915 stand out, respectively) but with a noticeable > component elsewhere (mm patches mainly through Andrew, some fs > updatres, radix tree test updates etc). > > Shortlog appended with details, go forth and test. I think we're in > fine shape for this stage in the development kernel, it shouldn't be > particularly scary to just say "I'll be a bit adventurous and test an > rc2 kernel". Yes, it's early rc time still, but go on, help us make > sure we're doing ok.. I thought it might just be me, but at least one other person doesn't see the v4.11-rc2 tag in git yet. The patch is on kernel.org though, so it's confusing. Did you forget to push it out? josh
Linux 4.11-rc2
ser range check and unused variables Jonathan McDowell (1): [media] dw2102: don't do DMA on stack Josh Poimboeuf (1): objtool: Fix another GCC jump table detection issue Kieran Bingham (1): [media] v4l: vsp1: Adapt vsp1_du_setup_lif() interface to use a structure Kirill A. Shutemov (9): x86/cpufeature: Add 5-level paging detection asm-generic: introduce 5level-fixup.h asm-generic: introduce __ARCH_USE_5LEVEL_HACK arch, mm: convert all architectures to use 5level-fixup.h asm-generic: introduce mm: convert generic code to 5-level paging mm: introduce __p4d_alloc() rmap: fix NULL-pointer dereference on THP munlocking thp: fix another corner case of munlock() vs. THPs Krzysztof Kozlowski (1): serial: samsung: Continue to work if DMA request fails Kunihiko Hayashi (1): pinctrl: uniphier: change pin names of aio/xirq for LD11 Laurent Dufour (1): mm/cgroup: avoid panic when init with low memory Laurentiu Tudor (1): powerpc/booke: Fix boot crash due to null hugepd Len Brown (1): cpufreq: Add the "cpufreq.off=1" cmdline option Linu Cherian (4): KVM: Add documentation for KVM_CAP_NR_MEMSLOTS KVM: arm/arm64: Enable KVM_CAP_NR_MEMSLOTS on arm/arm64 KVM: arm/arm64: Remove KVM_PRIVATE_MEM_SLOTS definition that are unused KVM: arm64: Increase number of user memslots to 512 Linus Torvalds (3): sched/headers: fix up header file dependency on overlayfs: remove now unnecessary header file include Linux 4.11-rc2 Marc Zyngier (2): arm64: KVM: VHE: Clear HCR_TGE when invalidating guest TLBs KVM: arm/arm64: vgic-v3: Don't pretend to support IRQ/FIQ bypass Marek Vasut (1): drm: mxsfb: Fix crash when provided invalid DT bindings Mark Rutland (2): arm: KVM: Survive unknown traps from guests arm64: KVM: Survive unknown traps from guests Martin Schwidefsky (6): s390/crypt: fix missing unlock in ctr_paes_crypt on error path s390: fix in-kernel program checks s390/cputime: remove last traces of cputime_t s390/cputime: reset all accounting fields on fork s390/cputime: provide archicture specific cputime_to_nsecs s390/timex: micro optimization for tod_to_ns Masahiro Yamada (2): scripts/spelling.txt: add "disble(d)" pattern and fix typo instances scripts/spelling.txt: add "overide" pattern and fix typo instances Masami Hiramatsu (1): kprobes/x86: Fix kernel panic when certain exception-handling addresses are probed Masanari Iida (4): xenbus: Remove duplicate inclusion of linux/init.h x86/vmware: Remove duplicate inclusion of asm/timer.h x86/intel_rdt: Remove duplicate inclusion of linux/cpu.h drivers/md/bcache/util.h: remove duplicate inclusion of blkdev.h Matjaz Hegedic (3): x86/reboot/quirks: Add ASUS EeeBook X205TA reboot quirk x86/reboot/quirks: Add ASUS EeeBook X205TA/W reboot quirk x86/reboot/quirks: Fix typo in ASUS EeeBook X205TA reboot quirk Matthew Wilcox (3): radix tree test suite: Depend on Makefile and quieten grep ida: Free correct IDA bitmap radix tree test suite: Specify -m32 in LDFLAGS too Mian Yousaf Kaukab (1): irqdomain: Add empty irq_domain_check_msi_remap Michael Ellerman (3): powerpc/64: Fix L1D cache shape vector reporting L1I values powerpc: Sort the selects under CONFIG_PPC radix tree test suite: Fix build with --as-needed Mike Rapoport (1): userfaultfd: non-cooperative: fix fork fctx->new memleak Min He (2): drm/i915/gvt: introduced failsafe mode into vgpu drm/i915/gvt: enter failsafe mode when guest requires more resources Ming Lei (4): blk-mq: initialize mq kobjects in blk_mq_init_allocated_queue() blk-mq: make lifetime consitent between q/ctx and its kobject blk-mq: make lifetime consistent between hctx and its kobject blk-mq: free hctx->cpumask in release handler of hctx's kobject NeilBrown (1): blk: improve order of bio handling in generic_make_request() Nicholas Piggin (1): powerpc: Fix compiling a BE kernel with a powerpc64le toolchain OGAWA Hirofumi (1): fat: fix using uninitialized fields of fat_inode/fsinfo_inode Paul Mackerras (1): powerpc/64: Invalidate process table caching after setting process table Pei Zhang (2): drm/i915/gvt: add cmd_access to GEN7_HALF_SLICE_CHICKEN1 drm/i915/gvt: add some new MMIOs to cmd_access white list Peter Chen (2): usb: gadget: dummy_hcd: clear usb_gadget region before registration usb: host: xhci-dbg: HCIVERSION should be a binary number Peter Zijlstra (4): sched/fair: Make select_idle_cpu() more aggressive sched/core: Fix pick_next_task() for RT,DL sched/clock, x86/tsc: Rework the x86 'unstable' sched_clock() interface locking/lockdep: Add nest_lock integrity
Re: linux-4.11-rc1/drivers/gpu/drm/exynos/exynos5433_drm_decon.c:681: suspicious mask ?
On 09.03.2017 08:34, Inki Dae wrote:
> Hello David,
>
> Thanks for report.
>
> 2017년 03월 06일 19:05에 David Binderman 이(가) 쓴 글:
>> Hello there,
>>
>> linux-4.11-rc1/drivers/gpu/drm/exynos/exynos5433_drm_decon.c:681]: (warning)
>> Result of operator '|' is always true if one operand is non-zero. Did you
>> intend to use '&'?
>>
> Right. this is known issue and below patch fixes this,
> http://www.spinics.net/lists/dri-devel/msg132589.html
>
> This patch will go to -fixes.
>
>> Source code is
>>
>> if (ctx->out_type | I80_HW_TRG) {
>>
>> Also in the same file:
>>
>> [drivers/gpu/drm/exynos/exynos5433_drm_decon.c:131]: (style) Same expression
>> on both sides of '|'.
>>
>> Source code is
>>
>>writel(TRIGCON_TE_AUTO_MASK | TRIGCON_SWTRIGEN
>>| TRIGCON_TE_AUTO_MASK | TRIGCON_SWTRIGEN,
> In this case, only problem is two flags are set in duplicate. This should be
> cleaned up. Thanks. :)
Wrong copy/paste removed two other flags and duplicated these above. It
did not hurt to much as it affects only software trigger which is not
used atm.
Fix sent yesterday [1].
[1]: http://www.spinics.net/lists/dri-devel/msg134877.html
Regards
Andrzej
>
>> Regards
>>
>> David Binderman
>>
>>
> ___
> dri-devel mailing list
> [email protected]
> https://lists.freedesktop.org/mailman/listinfo/dri-devel
Re: linux-4.11-rc1/drivers/gpu/drm/exynos/exynos5433_drm_decon.c:681: suspicious mask ?
Hello David,
Thanks for report.
2017년 03월 06일 19:05에 David Binderman 이(가) 쓴 글:
> Hello there,
>
> linux-4.11-rc1/drivers/gpu/drm/exynos/exynos5433_drm_decon.c:681]: (warning)
> Result of operator '|' is always true if one operand is non-zero. Did you
> intend to use '&'?
>
Right. this is known issue and below patch fixes this,
http://www.spinics.net/lists/dri-devel/msg132589.html
This patch will go to -fixes.
> Source code is
>
> if (ctx->out_type | I80_HW_TRG) {
>
> Also in the same file:
>
> [drivers/gpu/drm/exynos/exynos5433_drm_decon.c:131]: (style) Same expression
> on both sides of '|'.
>
> Source code is
>
>writel(TRIGCON_TE_AUTO_MASK | TRIGCON_SWTRIGEN
>| TRIGCON_TE_AUTO_MASK | TRIGCON_SWTRIGEN,
In this case, only problem is two flags are set in duplicate. This should be
cleaned up. Thanks. :)
>
> Regards
>
> David Binderman
>
>
Re: linux-4.11-rc1/drivers/gpu/drm/exynos/exynos5433_drm_decon.c:681: suspicious mask ?
Hi David, Inki,
Thanks for reporting.
On 06.03.2017 11:05, David Binderman wrote:
> Hello there,
>
> linux-4.11-rc1/drivers/gpu/drm/exynos/exynos5433_drm_decon.c:681]: (warning)
> Result of operator '|' is always true if one operand is non-zero. Did you
> intend to use '&'?
>
> Source code is
>
> if (ctx->out_type | I80_HW_TRG) {
>
> Also in the same file:
>
> [drivers/gpu/drm/exynos/exynos5433_drm_decon.c:131]: (style) Same expression
> on both sides of '|'.
>
> Source code is
>
>writel(TRIGCON_TE_AUTO_MASK | TRIGCON_SWTRIGEN
>| TRIGCON_TE_AUTO_MASK | TRIGCON_SWTRIGEN,
This typo was already reported by:
- Ilia Mirkin, I have uploaded 2nd fixed version of the patch,
apparently the 1st version has been merged [1],
- Dan Carpenter, he posted also the fix[2],
- and now David.
I guess at the moment the best solution is to get Dan's patch.
[1]: https://patchwork.kernel.org/patch/9493177/
[2]: https://patchwork.kernel.org/patch/9571375/
Regards
Andrzej
>
> Regards
>
> David Binderman
> ___
> dri-devel mailing list
> [email protected]
> https://lists.freedesktop.org/mailman/listinfo/dri-devel
Re: Warning on boot on SAMA5D2 with Linux 4.11-rc1
David, Romain,
On Tue, 7 Mar 2017 16:17:03 +0100
David Engraf wrote:
> Am 07.03.2017 um 16:05 schrieb Romain Izard:
> > 2017-03-06 12:28 GMT+01:00 Romain Izard :
> >>
> >> While looking for another issue, I tried Linux 4.11-rc1 on a SAMA5D2
> >> Xplained
> >> board. The boot log contains the following warning:
> >>
> >> [0.10] [ cut here ]
> >> [0.10] WARNING: CPU: 0 PID: 1 at
> >> ../kernel/time/sched_clock.c:180 sched_clock_register+0x44/0x1e4
> >> [0.10] CPU: 0 PID: 1 Comm: swapper Not tainted 4.11.0-rc1+ #3
> >> [0.10] Hardware name: Atmel SAMA5
> >> [0.10] [] (unwind_backtrace) from []
> >> (show_stack+0x10/0x14)
> >> [0.10] [] (show_stack) from []
> >> (__warn+0xe0/0xf8)
> >> [0.10] [] (__warn) from []
> >> (warn_slowpath_null+0x20/0x28)
> >> [0.10] [] (warn_slowpath_null) from []
> >> (sched_clock_register+0x44/0x1e4)
> >> [0.10] [] (sched_clock_register) from []
> >> (tcb_clksrc_init+0x1ac/0x360)
> >> [0.10] [] (tcb_clksrc_init) from []
> >> (do_one_initcall+0xb4/0x15c)
> >> [0.10] [] (do_one_initcall) from []
> >> (kernel_init_freeable+0x134/0x1c4)
> >> [0.10] [] (kernel_init_freeable) from []
> >> (kernel_init+0x8/0x10c)
> >> [0.10] [] (kernel_init) from []
> >> (ret_from_fork+0x14/0x3c)
> >> [0.10] ---[ end trace 7ce9be9d7cf6f800 ]---
> >> [0.100012] sched_clock: 32 bits at 10MHz, resolution 96ns, wraps
> >> every 206986376143ns
> >>
> >> This is related to the following commit:
> >> 7b9f1d16e6d1 clocksource/drivers/tcb_clksrc: Use 32 bit tcb as sched_clock
> >>
> >> When we call sched_clock_register from tcb_clksrc_init from
> >> arch_initcall, we are too late as sched expects all the candidates for
> >> its clock to be registered before interrupts are enabled. This warning
> >> does not prevent the tcb clock from being used.
>
> I have no idea why sched_clock_register complains when interrupts are
> already enabled. Form the code it doesn't look like this is a real issue
> and it works for me.
>
> > After some more use with 4.11-rc1, I also noticed that the timestamp for
> > printk rolls over to 0 after only 413s. Reverting the aforementioned commit
> > fixes it.
>
> I had this issue as well so I proposed the following patch a few weeks ago.
I think both issues are related: the scheduler expect the sched clock to
registered before the sched_clock_postinit() exactly to prevent the
case you're describing below.
I'd recommend that we revert 7b9f1d16e6d1
("clocksource/drivers/tcb_clksrc: Use 32 bit tcb as sched_clock")
until we have a clean solution to update sched clock at runtime (if we
ever want to support that).
Note that Alexandre posted a patch series to let the tcb_clksource
register itself earlier in the boot [1], which should prevent the
problem we have here.
Regards,
Boris
[1]http://lists.infradead.org/pipermail/linux-arm-kernel/2016-June/435532.html
>
> Forwarded Message
> Betreff: [PATCH resend] timers, sched_clock: Update timeout for clock wrap
> Datum: Thu, 2 Mar 2017 10:02:16 +0100
> Von: David Engraf
> An: [email protected], [email protected]
> Kopie (CC): [email protected], David Engraf
>
>
> The scheduler clock framework may not use the correct timeout for the clock
> wrap. This happens when a new clock driver calls sched_clock_register()
> after the kernel called sched_clock_postinit(). In this case the clock wrap
> timeout is too long thus sched_clock_poll() is called too late and the clock
> already wrapped.
>
> On my ARM system the scheduler was no longer scheduling any other task than
> the idle task because the sched_clock() wrapped.
>
> Signed-off-by: David Engraf
> ---
> kernel/time/sched_clock.c | 5 +
> 1 file changed, 5 insertions(+)
>
> diff --git a/kernel/time/sched_clock.c b/kernel/time/sched_clock.c
> index a26036d..382b159 100644
> --- a/kernel/time/sched_clock.c
> +++ b/kernel/time/sched_clock.c
> @@ -205,6 +205,11 @@ sched_clock_register(u64 (*read)(void), int bits,
> unsigned long rate)
> update_clock_read_data(&rd);
> + if (sched_clock_timer.function != NULL) {
> + /* update timeout for clock wrap */
> + hrtimer_start(&sched_clock_timer, cd.wrap_kt, HRTIMER_MODE_REL);
> + }
> +
> r = rate;
> if (r >= 400) {
> r /= 100;
Re: Warning on boot on SAMA5D2 with Linux 4.11-rc1
Am 07.03.2017 um 16:05 schrieb Romain Izard: 2017-03-06 12:28 GMT+01:00 Romain Izard : While looking for another issue, I tried Linux 4.11-rc1 on a SAMA5D2 Xplained board. The boot log contains the following warning: [0.10] [ cut here ] [0.10] WARNING: CPU: 0 PID: 1 at ../kernel/time/sched_clock.c:180 sched_clock_register+0x44/0x1e4 [0.10] CPU: 0 PID: 1 Comm: swapper Not tainted 4.11.0-rc1+ #3 [0.10] Hardware name: Atmel SAMA5 [0.10] [] (unwind_backtrace) from [] (show_stack+0x10/0x14) [0.10] [] (show_stack) from [] (__warn+0xe0/0xf8) [0.10] [] (__warn) from [] (warn_slowpath_null+0x20/0x28) [0.10] [] (warn_slowpath_null) from [] (sched_clock_register+0x44/0x1e4) [0.10] [] (sched_clock_register) from [] (tcb_clksrc_init+0x1ac/0x360) [0.10] [] (tcb_clksrc_init) from [] (do_one_initcall+0xb4/0x15c) [0.10] [] (do_one_initcall) from [] (kernel_init_freeable+0x134/0x1c4) [0.10] [] (kernel_init_freeable) from [] (kernel_init+0x8/0x10c) [0.10] [] (kernel_init) from [] (ret_from_fork+0x14/0x3c) [0.10] ---[ end trace 7ce9be9d7cf6f800 ]--- [0.100012] sched_clock: 32 bits at 10MHz, resolution 96ns, wraps every 206986376143ns This is related to the following commit: 7b9f1d16e6d1 clocksource/drivers/tcb_clksrc: Use 32 bit tcb as sched_clock When we call sched_clock_register from tcb_clksrc_init from arch_initcall, we are too late as sched expects all the candidates for its clock to be registered before interrupts are enabled. This warning does not prevent the tcb clock from being used. I have no idea why sched_clock_register complains when interrupts are already enabled. Form the code it doesn't look like this is a real issue and it works for me. After some more use with 4.11-rc1, I also noticed that the timestamp for printk rolls over to 0 after only 413s. Reverting the aforementioned commit fixes it. I had this issue as well so I proposed the following patch a few weeks ago. Forwarded Message Betreff: [PATCH resend] timers, sched_clock: Update timeout for clock wrap Datum: Thu, 2 Mar 2017 10:02:16 +0100 Von: David Engraf An: [email protected], [email protected] Kopie (CC): [email protected], David Engraf The scheduler clock framework may not use the correct timeout for the clock wrap. This happens when a new clock driver calls sched_clock_register() after the kernel called sched_clock_postinit(). In this case the clock wrap timeout is too long thus sched_clock_poll() is called too late and the clock already wrapped. On my ARM system the scheduler was no longer scheduling any other task than the idle task because the sched_clock() wrapped. Signed-off-by: David Engraf --- kernel/time/sched_clock.c | 5 + 1 file changed, 5 insertions(+) diff --git a/kernel/time/sched_clock.c b/kernel/time/sched_clock.c index a26036d..382b159 100644 --- a/kernel/time/sched_clock.c +++ b/kernel/time/sched_clock.c @@ -205,6 +205,11 @@ sched_clock_register(u64 (*read)(void), int bits, unsigned long rate) update_clock_read_data(&rd); + if (sched_clock_timer.function != NULL) { + /* update timeout for clock wrap */ + hrtimer_start(&sched_clock_timer, cd.wrap_kt, HRTIMER_MODE_REL); + } + r = rate; if (r >= 400) { r /= 100; -- 2.9.3
Re: Warning on boot on SAMA5D2 with Linux 4.11-rc1
2017-03-06 12:28 GMT+01:00 Romain Izard : > > While looking for another issue, I tried Linux 4.11-rc1 on a SAMA5D2 Xplained > board. The boot log contains the following warning: > > [0.10] [ cut here ] > [0.10] WARNING: CPU: 0 PID: 1 at > ../kernel/time/sched_clock.c:180 sched_clock_register+0x44/0x1e4 > [0.10] CPU: 0 PID: 1 Comm: swapper Not tainted 4.11.0-rc1+ #3 > [0.10] Hardware name: Atmel SAMA5 > [0.10] [] (unwind_backtrace) from [] > (show_stack+0x10/0x14) > [0.10] [] (show_stack) from [] (__warn+0xe0/0xf8) > [0.10] [] (__warn) from [] > (warn_slowpath_null+0x20/0x28) > [0.10] [] (warn_slowpath_null) from [] > (sched_clock_register+0x44/0x1e4) > [0.10] [] (sched_clock_register) from [] > (tcb_clksrc_init+0x1ac/0x360) > [0.10] [] (tcb_clksrc_init) from [] > (do_one_initcall+0xb4/0x15c) > [0.10] [] (do_one_initcall) from [] > (kernel_init_freeable+0x134/0x1c4) > [0.10] [] (kernel_init_freeable) from [] > (kernel_init+0x8/0x10c) > [0.10] [] (kernel_init) from [] > (ret_from_fork+0x14/0x3c) > [0.10] ---[ end trace 7ce9be9d7cf6f800 ]--- > [0.100012] sched_clock: 32 bits at 10MHz, resolution 96ns, wraps > every 206986376143ns > > This is related to the following commit: > 7b9f1d16e6d1 clocksource/drivers/tcb_clksrc: Use 32 bit tcb as sched_clock > > When we call sched_clock_register from tcb_clksrc_init from > arch_initcall, we are too late as sched expects all the candidates for > its clock to be registered before interrupts are enabled. This warning > does not prevent the tcb clock from being used. > After some more use with 4.11-rc1, I also noticed that the timestamp for printk rolls over to 0 after only 413s. Reverting the aforementioned commit fixes it. -- Romain Izard
Re: linux-next: stats (Was: Linux 4.11-rc1)
Hi, On Mon, Mar 06, 2017 at 10:52:00AM +1100, Stephen Rothwell wrote: > > - a couple of subsystems. drm, Infiniband, watchdog and btrfs stand out. > Top ten first word of commit summary: ... > 61 btrfs I can comment on the btrfs part. We have lots of cleanups for 4.11 and good part of all the patches are changing function parameters, one per patch. Therefore the overall counts are high. The first batch has been in for-next since mid Jan, and the second one was added right after to the beginning of the merge window (20170221). All series merged had appeared on the mailinglist a few days before 4.10 release but had to be updated due to some fixes regarding whitespace and over-80-char lines. So strictly speaking the patches did come late, but there was very low risk of breakage. Getting all the queued cleanups out is a relief as they tend to cause merge conflicts with pending patchsets.
Warning on boot on SAMA5D2 with Linux 4.11-rc1
Hello, While looking for another issue, I tried Linux 4.11-rc1 on a SAMA5D2 Xplained board. The boot log contains the following warning: [0.10] [ cut here ] [0.10] WARNING: CPU: 0 PID: 1 at ../kernel/time/sched_clock.c:180 sched_clock_register+0x44/0x1e4 [0.10] CPU: 0 PID: 1 Comm: swapper Not tainted 4.11.0-rc1+ #3 [0.10] Hardware name: Atmel SAMA5 [0.10] [] (unwind_backtrace) from [] (show_stack+0x10/0x14) [0.10] [] (show_stack) from [] (__warn+0xe0/0xf8) [0.10] [] (__warn) from [] (warn_slowpath_null+0x20/0x28) [0.10] [] (warn_slowpath_null) from [] (sched_clock_register+0x44/0x1e4) [0.10] [] (sched_clock_register) from [] (tcb_clksrc_init+0x1ac/0x360) [0.10] [] (tcb_clksrc_init) from [] (do_one_initcall+0xb4/0x15c) [0.10] [] (do_one_initcall) from [] (kernel_init_freeable+0x134/0x1c4) [0.10] [] (kernel_init_freeable) from [] (kernel_init+0x8/0x10c) [0.10] [] (kernel_init) from [] (ret_from_fork+0x14/0x3c) [0.10] ---[ end trace 7ce9be9d7cf6f800 ]--- [0.100012] sched_clock: 32 bits at 10MHz, resolution 96ns, wraps every 206986376143ns This is related to the following commit: 7b9f1d16e6d1 clocksource/drivers/tcb_clksrc: Use 32 bit tcb as sched_clock When we call sched_clock_register from tcb_clksrc_init from arch_initcall, we are too late as sched expects all the candidates for its clock to be registered before interrupts are enabled. This warning does not prevent the tcb clock from being used. -- Romain Izard
linux-next: stats (Was: Linux 4.11-rc1)
Hi Linus, On Sun, 5 Mar 2017 13:41:04 -0800 Linus Torvalds wrote: > > It _does_ feel like there was more stuff that I was asked to pull than > was in linux-next. That always happens, but seems to have happened > more now than usually. Comparing to the linux-next tree at the time of > the 4.10 release, almost 18% of the non-merge commits were not in > Linux-next. That seems higher than usual, although I guess Stephen > Rothwell has actual numbers from past merges. > > Now, about a quarter of the patches that weren't in linux-next do end > up having the same patch ID as something that was, so some of it was > due to just rebasing. But still - we have about 13% of the merge > window that wasn't in linux-next when 4.10 was released. > > Looking at the sources of that, there's a few different classes: > > - fixes. > >This is obviously ok and inevitable. I don't expect everything to > have been in linux-next, after all. > > - the statx() systen call thing. > >Yeah, I'll allow this one too, because quite frankly, the first > version of that patch was posted over six years ago. > > - there's the quite noticeable split-up series > >This one was posted and discussed before the merge window, and > needed to be merged late (and even then caused some conflicts). So it > had real reasons for late inclusion. > > - a couple of subsystems. drm, Infiniband, watchdog and btrfs stand out. My stats: As usual, the executive friendly graph is at http://neuling.org/linux-next-size.html :-) (No merge commits counted, next-20170220 was the first linux-next after the merge window opened.) Commits in v4.11-rc1 (relative to v4.10): 10960 Commits in next-20170220: 9791 Commits with the same SHA1: 9016 Commits with the same patch_id: 479 (1) Commits with the same subject line: 68 (1) (1) not counting those in the lines above. So commits in -rc1 that were in next-20170220: 9563 87% [ v4.10-rc1 like this: Commits in v4.10-rc1 (relative to v4.9): 11455 Commits in next-20161212: 10625 Commits with the same SHA1: 9927 Commits with the same patch_id: 437 (1) Commits with the same subject line: 25 (1) (1) not counting those in the lines above. So commits in -rc1 that were in next-20161212: 10389 90% And v4.9-rc1 like this: Commits in v4.9-rc1 (relative to v4.8):14308 Commits in next-20161004: 13539 Commits with the same SHA1:12716 Commits with the same patch_id: 485 (1) Commits with the same subject line: 33 (1) (1) not counting those in the lines above. So commits in -rc1 that were in next-20161004: 13234 92% So this time we have slightly more rebasing and overall more "extra" commits. ] Some breakdown of the list of extra commits (relative to next-20170220) in -rc1: Top ten first word of commit summary: 142 sched 117 drm 72 net 66 ib 63 watchdog 61 btrfs 60 scsi 48 f2fs 43 tools 29 perf Top ten authors: 146 [email protected] 46 [email protected] 45 [email protected] 39 [email protected] 32 [email protected] 32 [email protected] 28 [email protected] 26 [email protected] 22 [email protected] 21 [email protected] Top ten commiters: 217 [email protected] 161 [email protected] 88 [email protected] 79 [email protected] 64 [email protected] 63 [email protected] 59 [email protected] 58 [email protected] 57 [email protected] 52 [email protected] There are also 229 commits in next-20170220 that didn't make it into v4.11-rc1. Top ten first word of commit summary: 19 mm 18 arm 12 edac 9 keys 9 befs 7 random 6 target 6 coresight 6 bf609 5 edac.txt Top ten authors: 19 [email protected] 17 [email protected] 11 [email protected] 10 [email protected] 9 [email protected] 8 [email protected] 7 [email protected] 6 [email protected] 5 [email protected] 4 [email protected] Some of Andrew's patches are fixes for other patches in his tree (and have been merged into those). Top ten commiters: 76 [email protected] 20 [email protected] 16 steven@ubuntu-virtualbox.(none) 11 [email protected] 10 [email protected] 9 [email protected] 8 [email protected] 7 [email protected] 7 [email protected] 6 [email protected] Those commits by me are from the quilt series (mainly Andrew's mmotm tree). The steven@ubuntu-virtualbox.(none) ones are form a very out of date blackfin tree that has now been removed from linux-next. -- Chee
Linux 4.11-rc1
So two weeks have passed, the merge window is over, and 4.11-rc1 has been tagged and pushed out. This looks like a fairly regular release. It's on the smallish side, but mainly just compared to 4.9 and 4.10 - so it's not really _unusually_ small (in recent kernels, 4.1, 4.3, 4.5, 4.7 and now 4.11 all had about the same number of commits in the merge window). It _does_ feel like there was more stuff that I was asked to pull than was in linux-next. That always happens, but seems to have happened more now than usually. Comparing to the linux-next tree at the time of the 4.10 release, almost 18% of the non-merge commits were not in Linux-next. That seems higher than usual, although I guess Stephen Rothwell has actual numbers from past merges. Now, about a quarter of the patches that weren't in linux-next do end up having the same patch ID as something that was, so some of it was due to just rebasing. But still - we have about 13% of the merge window that wasn't in linux-next when 4.10 was released. Looking at the sources of that, there's a few different classes: - fixes. This is obviously ok and inevitable. I don't expect everything to have been in linux-next, after all. - the statx() systen call thing. Yeah, I'll allow this one too, because quite frankly, the first version of that patch was posted over six years ago. - there's the quite noticeable split-up series This one was posted and discussed before the merge window, and needed to be merged late (and even then caused some conflicts). So it had real reasons for late inclusion. - a couple of subsystems. drm, Infiniband, watchdog and btrfs stand out. That last case is what I found rather annoying this merge window. In particular, if you cannot follow the simple merge window rules (this whole two-week merge window and linux-next process has been in place over a decade), at least make the end result look good. Make it all look easy and problem-free. Make it look like you know what you're doing, and make damn sure the code was tested exhaustively some other way. Because if you bypass the linux-next sanity checks, you had better have your own sanity checks that you replaced them with. Or you just need to be _so_ good that nobody minds you bypassing them, and nobody ever notices your shortcuts. Saying "screw all the rules and processes we have in place to verify things", and then sending me crap that doesn't even build for me is _not_ acceptable. You people know who you are. Next merge window I will not accept anything even remotely like that. Things that haven't been in linux-next will be rejected, and since you're already on my shit-list you'll get shouted at again. Linus --- Al Viro (4): vfs sendmsg updates vfs pile two vfs 'statx()' update misc final vfs updates Alex Williamson (1): VFIO updates Alexandre Belloni (1): RTC updates Andrew Morton (3): updates more updates yet more updates Anna Schumaker (1): NFS client updates Arnd Bergmann (8): ARM SoC non-urgent fixes ARM SoC platform updates ARM SoC 64-bit updates ARM SoC defconfig updates ARM DT updates ARM 64-bit DT updates ARM SoC driver updates ARM SoC late DT updates Bartlomiej Zolnierkiewicz (1): fbdev updates Bjorn Andersson (2): remoteproc updates rpmsg updates Bjorn Helgaas (2): PCI updates PCI fixes Bob Peterson (1): GFS2 fix Borislav Petkov (1): EDAC updates Brian Norris (1): MTD updates Bruce Fields (1): nfsd updates Chris Mason (2): btrfs updates more btrfs updates Corey Minyard (1): IPMI updates Dan Williams (1): libnvdimm fixes Darren Hart (1): x86 platform driver updates Darrick Wong (1): xfs updates Dave Airlie (3): drm updates drm fixes drm AST2500 support David Miller (6): networking updates networking fixes sparc updates networking fixes IDE updates networking fixes Dmitry Torokhov (1): input updates Doug Ledford (3): rdma updates Mellanox rdma updates rdma DMA mapping updates Eric Biederman (1): namespace updates Geert Uytterhoeven (1): m68k updates Greg KH (6): USB/PHY updates char/misc driver updates driver core updates staging/iio driver updates tty/serial driver updates staging/IIO driver fixes Greg Ungerer (1): m68nommu update Guenter Roeck (3): hwmon updates watchdog updates more watchdog updates Helge Deller (1): parisc fixes and cleanups Herbert Xu (2): crypto update crypto fixes Ilya Dryomov (1): ceph updates Ingo Molnar (23): debugobjects updates RCU updates EFI updates perf updates RAS updates scheduler updates locking updates x86 apic changes x86 asm update x86 boot updates x86 cleanups x86 cpufeature updates x86 fpu updates x86 microcode updates x86 mm updates x86 platform updates o
[GIT PULL] Please pull NFS client changes for Linux 4.11
Hi Linus, The following changes since commit 566cf877a1fcb6d6dc0126b076aad062054c2637: Linux 4.10-rc6 (2017-01-29 14:25:17 -0800) are available in the git repository at: git://git.linux-nfs.org/projects/anna/linux-nfs.git tags/nfs-for-4.11-1 for you to fetch changes up to ed92d8c137b7794c2c2aa14479298b9885967607: NFSv4: fix getacl ERANGE for some ACL buffer sizes (2017-02-23 17:23:35 -0500) Highlights include: Stable bugfixes: - NFSv4: Fix memory and state leak in _nfs4_open_and_get_state - xprtrdma: Fix Read chunk padding - xprtrdma: Per-connection pad optimization - xprtrdma: Disable pad optimization by default - xprtrdma: Reduce required number of send SGEs - nlm: Ensure callback code also checks that the files match - pNFS/flexfiles: If the layout is invalid, it must be updated before retrying - NFSv4: Fix reboot recovery in copy offload - Revert "NFSv4.1: Handle NFS4ERR_BADSESSION/NFS4ERR_DEADSESSION replies to OP_SEQUENCE" - NFSv4: fix getacl head length estimation - NFSv4: fix getacl ERANGE for sum ACL buffer sizes Features: - Add and use dprintk_cont macros - Various cleanups to NFS v4.x to reduce code duplication and complexity - Remove unused cr_magic related code - Improvements to sunrpc "read from buffer" code - Clean up sunrpc timeout code and allow changing TCP timeout parameters - Remove duplicate mw_list management code in xprtrdma - Add generic functions for encoding and decoding xdr streams Bugfixes: - Clean up nfs_show_mountd_netid - Fix sparse warnings - Properly handle -ERESTARTSYS in nfs_rename() - Check if register_shrinker() failed during rpcauth_init() - Properly clean up procfs/pipefs entries - Various NFS over RDMA related fixes - Silence uninitialized variable warning in sunrpc Thanks, Anna Anna Schumaker (21): NFS: Move nfs4_get_session() into nfs4_session.h NFS: Change nfs4_get_session() to take an nfs_client structure NFS: Change nfs4_setup_sequence() to take an nfs_client structure NFS: Use nfs4_setup_sequence() everywhere NFS: Create a single nfs4_setup_sequence() function NFS: Move slot-already-allocated check into nfs_setup_sequence() NFS: Lock the slot table from a single place during setup sequence NFS: Handle setup sequence task rescheduling in a single place NFS: Check if the slot table is draining from nfs4_setup_sequence() NFS: Merge the remaining setup_sequence functions NFS: Make trace_nfs4_setup_sequence() available to NFS v4.0 NFS: Fix inconsistent indentation in nfs4proc.c NFS: Clean up _nfs4_is_integrity_protected() NFS: Remove nfs4_wait_for_completion_rpc_task() NFS: Return errors directly in _nfs4_opendata_reclaim_to_nfs4_state() NFS: Remove an extra if in _nfs4_recover_proc_open() NFS: Remove nfs4_recover_expired_lease() NFS: Remove unnecessary goto in nfs4_lookup_root_sec() NFS: No need to set and return status in nfs41_lock_expired() NFS: Clean up nfs41_same_server_scope() NFS: Return the comparison result directly in nfs41_match_stateid() Benjamin Coddington (1): NFS: nfs_rename() handle -ERESTARTSYS dentry left behind Chuck Lever (9): xprtrdma: Fix Read chunk padding xprtrdma: Per-connection pad optimization xprtrdma: Disable pad optimization by default xprtrdma: Reduce required number of send SGEs xprtrdma: Shrink send SGEs array xprtrdma: Properly recover FRWRs with in-flight FASTREG WRs xprtrdma: Handle stale connection rejection xprtrdma: Refactor management of mw_list field sunrpc: Allow xprt->ops->timer method to sleep Dan Carpenter (1): sunrpc: silence uninitialized variable warning J. Bruce Fields (1): NFSv4: fix getacl head length estimation Joe Perches (1): sunrpc & nfs: Add and use dprintk_cont macros Kinglong Mee (7): sunrpc: error out if register_shrinker fail sunrpc/nfs: cleanup procfs/pipefs entry in cache_detail sunrpc: rename NFS_NGROUPS to UNX_NGROUPS for auth unix sunrpc: remove dead codes of cr_magic in rpc_cred sunrpc: update the comments of sunrpc proc path sunrpc: record rpc client pointer in seq->private directly sunrpc: use simple_read_from_buffer for reading cache flush NeilBrown (2): SUNRPC: two small improvements to rpcauth shrinker. NFS: tidy up nfs_show_mountd_netid Nicholas Piggin (1): nfs: no PG_private waiters remain, remove waker Trond Myklebust (17): NFSv4: Fix memory and state leak in _nfs4_open_and_get_state SUNRPC: Remove unused function rpc_get_timeout() SUNRPC: Refactor TCP socket timeout code into a helper function SUNRPC: Allow changing of the TCP timeout parameters on the fly NFSv4: Set the connection timeout to match the lease period nlm: Ensure callback code also checks that the files match SUNRPC: Add generic helper
Re: [GIT PULL] tpmdd fixes for Linux 4.11
On Tue, Feb 21, 2017 at 07:08:29PM +1100, James Morris wrote: > On Mon, 20 Feb 2017, Jarkko Sakkinen wrote: > > > Hi > > > > Some small scoped but needed fixes for the release. > > > > Pulled, just in time ;) > > > -- > James Morris > Thank you! /Jarkko
Re: [GIT PULL] tpmdd fixes for Linux 4.11
On Mon, 20 Feb 2017, Jarkko Sakkinen wrote: > Hi > > Some small scoped but needed fixes for the release. > Pulled, just in time ;) -- James Morris
[GIT PULL] tpmdd fixes for Linux 4.11
Hi Some small scoped but needed fixes for the release. /Jarkko The following changes since commit 52176603795c2ab7e9faf6bb94820da1b726aabd: KEYS: Use memzero_explicit() for secret data (2017-02-10 12:43:51 +1100) are available in the git repository at: git://git.infradead.org/users/jjs/linux-tpmdd.git tags/tpmdd-next-20170220 for you to fetch changes up to 61841be6358c03e864ad4c386c9a102edbba9cb8: tpm: declare tpm2_get_pcr_allocation() as static (2017-02-20 13:23:18 +0200) tpmdd fixes for Linux 4.11 Dmitry Torokhov (1): tpm: fix misspelled "facilitate" in module parameter description Jarkko Sakkinen (1): tpm: declare tpm2_get_pcr_allocation() as static Julia Lawall (1): tpm xen: drop unneeded chip variable Stefan Berger (1): tpm: Fix expected number of response bytes of TPM1.2 PCR Extend Wei Yongjun (1): tpm_tis: fix the error handling of init_tis() drivers/char/tpm/tpm-interface.c | 4 +- drivers/char/tpm/tpm.h | 1 - drivers/char/tpm/tpm2-cmd.c | 94 +++- drivers/char/tpm/tpm_tis.c | 2 +- drivers/char/tpm/xen-tpmfront.c | 2 - 5 files changed, 48 insertions(+), 55 deletions(-)
Re: [GIT PULL] tpmdd updates for Linux 4.11
On Fri, 3 Feb 2017, Jarkko Sakkinen wrote: > Hi > > This is the second flush of updates for 4.11. > > The pull request include two new features: > > 1. Extension to tpm_pcr_extend() (used by IMA) to extend all PCR banks > instead of just SHA-1 banks. It is recommended by TCG to do so in order > to prevent malicious use of PCRs. > 2. TPM 2.0 event log with backend support for OF device tree. > > /Jarkko > > The following changes since commit 20f482ab9e0f800d1e01ce748ebd382d085abe56: > > ima: allow to check MAY_APPEND (2017-01-27 14:17:21 -0500) > > are available in the git repository at: > > git://git.infradead.org/users/jjs/linux-tpmdd.git tags/tpmdd-next-20170204 > Pulled, thanks! -- James Morris
[GIT PULL] tpmdd updates for Linux 4.11
Hi
This is the second flush of updates for 4.11.
The pull request include two new features:
1. Extension to tpm_pcr_extend() (used by IMA) to extend all PCR banks
instead of just SHA-1 banks. It is recommended by TCG to do so in order
to prevent malicious use of PCRs.
2. TPM 2.0 event log with backend support for OF device tree.
/Jarkko
The following changes since commit 20f482ab9e0f800d1e01ce748ebd382d085abe56:
ima: allow to check MAY_APPEND (2017-01-27 14:17:21 -0500)
are available in the git repository at:
git://git.infradead.org/users/jjs/linux-tpmdd.git tags/tpmdd-next-20170204
for you to fetch changes up to 70ea163699b68963e222a905e184f6436e8a290d:
tpm: silence an array overflow warning (2017-02-03 22:33:55 +0200)
tpmdd updates for Linux 4.11
Dan Carpenter (1):
tpm: silence an array overflow warning
Jarkko Sakkinen (2):
tpm: remove tpm_read_index and tpm_write_index from tpm.h
tpm: fix RC value check in tpm2_seal_trusted
Jason Gunthorpe (1):
tpm: Begin the process to deprecate user_read_timer
Maciej S. Szmigiero (1):
tpm_tis: fix iTPM probe via probe_itpm() function
Nayna Jain (4):
tpm: implement TPM 2.0 capability to get active PCR banks
tpm: enhance TPM 2.0 PCR extend to support multiple banks
tpm: enhance read_log_of() to support Physical TPM event log
tpm: add securityfs support for TPM 2.0 firmware event log
Stefan Berger (1):
tpm: fix the type of owned field in cap_t
drivers/char/tpm/Kconfig | 1 +
drivers/char/tpm/Makefile | 2 +-
drivers/char/tpm/tpm-dev.c | 5 +-
drivers/char/tpm/tpm-interface.c | 14 +-
drivers/char/tpm/tpm.h | 39 ++--
.../char/tpm/{tpm_eventlog.c => tpm1_eventlog.c} | 35 ++--
drivers/char/tpm/tpm2-cmd.c| 170 -
drivers/char/tpm/tpm2_eventlog.c | 203 +
drivers/char/tpm/tpm_acpi.c| 3 +
drivers/char/tpm/tpm_atmel.h | 6 +
drivers/char/tpm/tpm_eventlog.h| 51 +-
drivers/char/tpm/tpm_nsc.c | 12 ++
drivers/char/tpm/tpm_of.c | 27 ++-
drivers/char/tpm/tpm_tis_core.c| 25 +--
14 files changed, 497 insertions(+), 96 deletions(-)
rename drivers/char/tpm/{tpm_eventlog.c => tpm1_eventlog.c} (95%)
create mode 100644 drivers/char/tpm/tpm2_eventlog.c
Re: [GIT PULL] tpmdd updates for Linux 4.11
On Mon, 23 Jan 2017, Jarkko Sakkinen wrote: > Hi > > This pull request contains tpmdd updates for Linux 4.11. This release > contains only bug fixes and minor enhancements. > > /Jarkko > > The following changes since commit b25e67161c295c98acda92123b2dd1e7d8642901: > > seccomp: dump core when using SECCOMP_RET_KILL (2017-01-23 21:42:42 +1100) > > are available in the git repository at: > > git://git.infradead.org/users/jjs/linux-tpmdd.git tags/tpmdd-next-20170123 > Pulled, thanks! -- James Morris
[GIT PULL] tpmdd updates for Linux 4.11
Hi This pull request contains tpmdd updates for Linux 4.11. This release contains only bug fixes and minor enhancements. /Jarkko The following changes since commit b25e67161c295c98acda92123b2dd1e7d8642901: seccomp: dump core when using SECCOMP_RET_KILL (2017-01-23 21:42:42 +1100) are available in the git repository at: git://git.infradead.org/users/jjs/linux-tpmdd.git tags/tpmdd-next-20170123 for you to fetch changes up to c659af78eb7b7d7be40f23d9d97bde58eb1368ac: tpm: Check size of response before accessing data (2017-01-23 18:28:18 +0200) tpmdd updates for Linux 4.11 Corentin Labbe (1): tpm/st33zp24: Remove unneeded linux/miscdevice.h include Geliang Tang (1): tpm/tpm_tis_spi: drop duplicate header module.h Jason Gunthorpe (1): tpm: Do not print an error message when doing TPM auto startup Jiandi An (1): tpm, tpm_crb: Handle 64-bit resource in crb_check_resource() Maciej S. Szmigiero (1): tpm_tis: use default timeout value if chip reports it as zero Stefan Berger (1): tpm: Check size of response before accessing data Winkler, Tomas (4): tpm: add kdoc for tpm_transmit and tpm_transmit_cmd tpm/tpm2-chip: fix kdoc errors tmp: use pdev for parent device in tpm_chip_alloc tpm/vtpm: fix kdoc warnings drivers/char/tpm/st33zp24/st33zp24.c | 1 - drivers/char/tpm/tpm-chip.c | 8 +- drivers/char/tpm/tpm-interface.c | 159 ++-- drivers/char/tpm/tpm-sysfs.c | 28 -- drivers/char/tpm/tpm.h | 7 +- drivers/char/tpm/tpm2-cmd.c | 170 +-- drivers/char/tpm/tpm_crb.c | 8 +- drivers/char/tpm/tpm_ibmvtpm.c | 106 +++--- drivers/char/tpm/tpm_tis.c | 2 +- drivers/char/tpm/tpm_tis_core.c | 9 +- drivers/char/tpm/tpm_tis_core.h | 2 +- drivers/char/tpm/tpm_tis_spi.c | 1 - drivers/char/tpm/tpm_vtpm_proxy.c| 48 +++--- 13 files changed, 347 insertions(+), 202 deletions(-)
