From: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
To: Jeremy Linton <jeremy.linton@arm.com>
Cc: Davidlohr Bueso <dave@stgolabs.net>,
Peter Zijlstra <peterz@infradead.org>,
linux-kernel@vger.kernel.org, mingo@redhat.com,
josh@joshtriplett.org
Subject: Re: [PATCH] locktorture: Fix Oops when reader/writer count is 0
Date: Wed, 8 Nov 2017 09:44:19 -0800 [thread overview]
Message-ID: <20171108174419.GL3624@linux.vnet.ibm.com> (raw)
In-Reply-To: <dfa9eec3-f814-2752-5302-b78c3efed91d@arm.com>
On Wed, Nov 08, 2017 at 10:57:07AM -0600, Jeremy Linton wrote:
> On 11/08/2017 10:48 AM, Paul E. McKenney wrote:
> >On Wed, Nov 08, 2017 at 06:45:23AM -0800, Davidlohr Bueso wrote:
> >>On Tue, 07 Nov 2017, Paul E. McKenney wrote:
> >>
> >>>On Tue, Nov 07, 2017 at 10:07:48PM +0100, Peter Zijlstra wrote:
> >>>>On Tue, Nov 07, 2017 at 02:01:58PM -0600, Jeremy Linton wrote:
> >>>>>Hi,
> >>>>>
> >>>>>On 10/10/2017 10:52 AM, Jeremy Linton wrote:
> >>>>>>If nwriters_stress=0 is passed to the lock torture test
> >>>>>>it will panic in:
> >>>>>
> >>>>>Ping?
> >>>>>
> >>>>>Has anyone had a chance to look at this?
> >>>>
> >>>>Helps if you Cc the people actually working on this stuff of course...
> >>>
> >>>Thank you for the forward, Peter, I have queued Jeremy's patch for
> >>>testing and review.
> >>
> >>fyi I had proposed the following a while back, which I think is more
> >>complete than this patch:
> >>
> >>https://lkml.org/lkml/2017/5/15/201
> >>
> >>Ah, there's also this (unrelated) fix:
> >>https://lkml.org/lkml/2017/5/15/203
> >>
> >>>But Jeremy's list of email addresses is what you would expect from
> >>>looking at MAINTAINERS, so how about the following patch?
> >
> >And it looks like Jeremy was not alone -- I was not CCed on either
> >of those patches, either.
> >
> >Dave's patch does look more complete, and it certainly was submitted
> >first. Let's see if it still applies... And they both do.
>
> Yes, avoiding the zero length allocations is probably a good plan,
> and complaining if both the reader and writer are zero is doesn't
> hurt either.
>
> So, I'm good with that patch too..
>
> Reviewed-by: Jeremy Linton <jeremy.linton@arm.com>
Thank you!
> >Jeremy, could you please test Dave's patches and make sure that they
> >work for you? That way I can apply your Tested-by. Dave, any objection
> >to my adding Jeremy's Reported-by to your /201 patch?
>
> I will give it a spin..
Very good! Looking forward to seeing the results.
Thanx, Paul
> >>>------------------------------------------------------------------------
> >>>
> >>>commit 58322063498c8f5a3cc88f95bee237a0ce81f70a
> >>>Author: Paul E. McKenney <paulmck@linux.vnet.ibm.com>
> >>>Date: Tue Nov 7 14:10:03 2017 -0800
> >>>
> >>> torture: Place all torture-test modules in one MAINTAINERS group
> >>>
> >>> There is some confusion about where patches to kernel/torture.c
> >>> and kernel/locking/locktorture.c should be sent. This commit
> >>> therefore updates MAINTAINERS appropriately.
> >>>
> >>> Reported-by: Peter Zijlstra <peterz@infradead.org>
> >>> Signed-off-by: Paul E. McKenney <paulmck@linux.vnet.ibm.com>
> >>>
> >>>diff --git a/MAINTAINERS b/MAINTAINERS
> >>>index 2d3d750b19c0..eab868adedc6 100644
> >>>--- a/MAINTAINERS
> >>>+++ b/MAINTAINERS
> >>>@@ -8091,6 +8091,7 @@ F: arch/*/include/asm/rwsem.h
> >>>F: include/linux/seqlock.h
> >>>F: lib/locking*.[ch]
> >>>F: kernel/locking/
> >>>+X: kernel/locking/locktorture.c
> >>>
> >>>LOGICAL DISK MANAGER SUPPORT (LDM, Windows 2000/XP/Vista Dynamic Disks)
> >>>M: "Richard Russon (FlatCap)" <ldm@flatcap.org>
> >>>@@ -11318,15 +11319,6 @@ L: linux-wireless@vger.kernel.org
> >>>S: Orphan
> >>>F: drivers/net/wireless/ray*
> >>>
> >>>-RCUTORTURE MODULE
> >>>-M: Josh Triplett <josh@joshtriplett.org>
> >>>-M: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
> >>>-L: linux-kernel@vger.kernel.org
> >>>-S: Supported
> >>>-T: git git://git.kernel.org/pub/scm/linux/kernel/git/paulmck/linux-rcu.git
> >>>-F: Documentation/RCU/torture.txt
> >>>-F: kernel/rcu/rcutorture.c
> >>>-
> >>>RCUTORTURE TEST FRAMEWORK
> >>>M: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
> >>>M: Josh Triplett <josh@joshtriplett.org>
> >>>@@ -13558,6 +13550,18 @@ L: platform-driver-x86@vger.kernel.org
> >>>S: Maintained
> >>>F: drivers/platform/x86/topstar-laptop.c
> >>>
> >>>+TORTURE-TEST MODULES
> >>>+M: Davidlohr Bueso <dave@stgolabs.net>
> >>>+M: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
> >>>+M: Josh Triplett <josh@joshtriplett.org>
> >>>+L: linux-kernel@vger.kernel.org
> >>>+S: Supported
> >>>+T: git git://git.kernel.org/pub/scm/linux/kernel/git/paulmck/linux-rcu.git
> >>>+F: Documentation/RCU/torture.txt
> >>>+F: kernel/torture.c
> >>>+F: kernel/rcu/rcutorture.c
> >>>+F: kernel/locking/locktorture.c
> >>
> >>Sure, if you think this is the best way to go, I have no problem.
> >>
> >>Thanks,
> >>Davidlohr
> >>
> >
>
next prev parent reply other threads:[~2017-11-08 17:44 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-10 15:52 [PATCH] locktorture: Fix Oops when reader/writer count is 0 Jeremy Linton
2017-11-07 20:01 ` Jeremy Linton
2017-11-07 21:07 ` Peter Zijlstra
2017-11-07 22:15 ` Paul E. McKenney
2017-11-08 8:27 ` Peter Zijlstra
2017-11-08 14:17 ` Paul E. McKenney
2017-11-08 14:45 ` Davidlohr Bueso
2017-11-08 16:48 ` Paul E. McKenney
2017-11-08 16:57 ` Jeremy Linton
2017-11-08 17:44 ` Paul E. McKenney [this message]
2017-11-09 16:15 ` Jeremy Linton
2017-11-09 16:19 ` Davidlohr Bueso
2017-11-09 16:45 ` Paul E. McKenney
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20171108174419.GL3624@linux.vnet.ibm.com \
--to=paulmck@linux.vnet.ibm.com \
--cc=dave@stgolabs.net \
--cc=jeremy.linton@arm.com \
--cc=josh@joshtriplett.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox