From: Josh Boyer <jwboyer@redhat.com>
To: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Frederic Weisbecker <fweisbec@gmail.com>,
linux-kernel@vger.kernel.org
Subject: Re: 3.0-git15 Atomic scheduling in pidmap_init
Date: Thu, 18 Aug 2011 18:19:20 -0400 [thread overview]
Message-ID: <20110818221920.GR2227@zod.bos.redhat.com> (raw)
In-Reply-To: <20110818212334.GE2325@linux.vnet.ibm.com>
On Thu, Aug 18, 2011 at 02:23:34PM -0700, Paul E. McKenney wrote:
> > > I am sorry, but I didn't make the rules! And I must carry the fix
> > > longer as well, if that makes you feel any better.
> >
> > bah, we're not that anal. The patch fixes a bug and prevents a nasty
> > warning spew. Please, send it to Linus.
>
> Given your Acked-by and Josh's Tested-by I might consider it. ;-)
>
> Speaking of which, Josh, does this patch help Nicolas and Michal?
Yes, it did. The bug is closed because I included the patch. (I could
recreate it myself as well.)
> > We appear to be referring to the patch "rcu: Avoid having just-onlined
> > CPU resched itself when RCU is idle"? If so, the changelog doesn't
> > even mention that the patch fixes a scheduling-while-atomic warning and
> > the changelog fails to refer to the redhat bug report. These omissions
> > should be repaired, please.
>
> OK... But I cannot bring myself to believe that my fix does more than
> hide some other bug. Which is OK, I will just say that in the changelog.
I looked for this other bug myself for a while. I couldn't find it.
josh
next prev parent reply other threads:[~2011-08-18 22:19 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-01 15:46 Josh Boyer
2011-08-04 11:46 ` Josh Boyer
2011-08-04 14:04 ` Paul E. McKenney
2011-08-04 15:06 ` Josh Boyer
2011-08-04 16:26 ` Paul E. McKenney
2011-08-04 17:31 ` Josh Boyer
2011-08-05 1:19 ` Josh Boyer
2011-08-05 6:56 ` Paul E. McKenney
2011-08-05 14:22 ` Josh Boyer
2011-08-05 17:08 ` Frederic Weisbecker
2011-08-05 22:26 ` Paul E. McKenney
2011-08-05 23:12 ` Frederic Weisbecker
2011-08-08 2:09 ` Paul E. McKenney
2011-08-08 2:55 ` Frederic Weisbecker
2011-08-08 3:10 ` Paul E. McKenney
2011-08-09 11:35 ` Frederic Weisbecker
2011-08-10 12:45 ` Josh Boyer
2011-08-10 14:53 ` Frederic Weisbecker
2011-08-10 15:03 ` Josh Boyer
2011-08-14 23:04 ` Paul E. McKenney
2011-08-15 14:04 ` Josh Boyer
2011-08-15 15:20 ` Paul E. McKenney
2011-08-17 22:37 ` Josh Boyer
2011-08-17 22:49 ` Paul E. McKenney
2011-08-17 23:02 ` Josh Boyer
2011-08-17 23:06 ` Frederic Weisbecker
2011-08-17 23:17 ` Josh Boyer
2011-08-18 18:35 ` Paul E. McKenney
2011-08-18 19:11 ` Josh Boyer
2011-08-18 21:00 ` Andrew Morton
2011-08-18 21:23 ` Paul E. McKenney
2011-08-18 21:55 ` Paul E. McKenney
2011-08-18 22:21 ` Josh Boyer
2011-08-18 23:01 ` Paul E. McKenney
2011-08-24 22:45 ` Frederic Weisbecker
2011-08-24 23:12 ` Paul E. McKenney
2011-08-24 23:34 ` Frederic Weisbecker
2011-08-24 23:57 ` Paul E. McKenney
2011-08-18 22:19 ` Josh Boyer [this message]
2011-08-18 23:16 ` Paul E. McKenney
2011-08-18 23:27 ` Andrew Morton
2011-08-19 0:38 ` 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=20110818221920.GR2227@zod.bos.redhat.com \
--to=jwboyer@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=fweisbec@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=paulmck@linux.vnet.ibm.com \
/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
all inboxes | Powered by JetHome®