From: Ingo Molnar <mingo@elte.hu>
To: David Newall <davidn@davidnewall.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [PATCH] fix off-by-one in __iterator_load_balance
Date: Thu, 12 Mar 2009 11:02:05 +0100 [thread overview]
Message-ID: <20090312100205.GA30095@elte.hu> (raw)
In-Reply-To: <49B8D730.4030708@davidnewall.com>
* David Newall <davidn@davidnewall.com> wrote:
> David Newall wrote:
> > An off-by-one bug in __iterator_load_balance causes it to erroneously
> > return NULL if the next task on the list is also the last entry in the
> > list. This patch corrects that fault.
> >
>
> Patch withdrawn. Who'd have thought 2.6.27.19 was so out of date?
Yeah, the 2.6.27 -> latest-sched-devel distance is more than 250
commits already - that's a lot of commits for the scheduler
which is only 15 KLOC. Patches done on .27 are unlikely to apply
- and bugs are often fixed already.
Ingo
prev parent reply other threads:[~2009-03-12 10:02 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-11 14:49 [PATCH] fix off-by-one in __iterator_load_balance David Newall
2009-03-12 9:34 ` David Newall
2009-03-12 10:02 ` Ingo Molnar [this message]
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=20090312100205.GA30095@elte.hu \
--to=mingo@elte.hu \
--cc=akpm@linux-foundation.org \
--cc=davidn@davidnewall.com \
--cc=linux-kernel@vger.kernel.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