From: Anna-Maria Gleixner <anna-maria@linutronix.de>
To: Thomas Gleixner <tglx@linutronix.de>
Cc: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>,
"Eric W. Biederman" <ebiederm@xmission.com>,
Sebastian Andrzej Siewior <bigeasy@linutronix.de>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] kernel/signal: Remove no longer required irqsave/restore
Date: Tue, 8 May 2018 15:42:25 +0200 (CEST) [thread overview]
Message-ID: <alpine.DEB.2.20.1805081539060.2262@hypnos.tec.linutronix.de> (raw)
In-Reply-To: <alpine.DEB.2.21.1805050755240.1685@nanos.tec.linutronix.de>
On Sat, 5 May 2018, Thomas Gleixner wrote:
> On Fri, 4 May 2018, Paul E. McKenney wrote:
> > On Fri, May 04, 2018 at 11:38:37PM -0500, Eric W. Biederman wrote:
> > > > (Me, I would run rcutorture scenario TREE03 for an extended time period
> > > > on b4abf91047cf with your patch applied.
> >
> > And with lockdep enabled, which TREE03 does not do by default.
>
> Will run that again to make sure.
>
I ran the rcutorture scenario TREE03 for 4 hours with the above
described setup. It was successful and without any lockdep splats.
Anna-Maria
next prev parent reply other threads:[~2018-05-08 13:42 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-04 14:40 [PATCH] kernel/signal: Remove no longer required irqsave/restore Sebastian Andrzej Siewior
2018-05-04 16:59 ` Eric W. Biederman
2018-05-04 17:04 ` Sebastian Andrzej Siewior
2018-05-04 17:17 ` Eric W. Biederman
2018-05-04 17:52 ` Paul E. McKenney
2018-05-04 19:03 ` Eric W. Biederman
2018-05-04 19:45 ` Paul E. McKenney
2018-05-04 20:08 ` Eric W. Biederman
2018-05-04 20:37 ` Paul E. McKenney
2018-05-05 4:38 ` Eric W. Biederman
2018-05-05 5:25 ` Paul E. McKenney
2018-05-05 5:56 ` Thomas Gleixner
2018-05-08 13:42 ` Anna-Maria Gleixner [this message]
2018-05-08 14:53 ` Paul E. McKenney
2018-05-08 15:49 ` Anna-Maria Gleixner
2018-05-08 16:53 ` Paul E. McKenney
2018-06-07 20:21 ` [tip:core/urgent] signal: " tip-bot for Anna-Maria Gleixner
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=alpine.DEB.2.20.1805081539060.2262@hypnos.tec.linutronix.de \
--to=anna-maria@linutronix.de \
--cc=bigeasy@linutronix.de \
--cc=ebiederm@xmission.com \
--cc=linux-kernel@vger.kernel.org \
--cc=paulmck@linux.vnet.ibm.com \
--cc=tglx@linutronix.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.