From: Eric Sandeen <sandeen@redhat.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Tejun Heo <htejun@gmail.com>, Maneesh Soni <maneesh@in.ibm.com>,
stable@kernel.org
Subject: Re: [stable] [PATCH] - fix oops in sysfs_readdir
Date: Mon, 21 May 2007 19:18:55 -0500 [thread overview]
Message-ID: <465236EF.40102@redhat.com> (raw)
In-Reply-To: <20070521153935.b549db8f.akpm@linux-foundation.org>
Andrew Morton wrote:
> On Mon, 21 May 2007 13:11:21 -0500
> Eric Sandeen <sandeen@redhat.com> wrote:
>
>> This is a non-ida backport of Tejun's patch in -mm at:
>> ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.22-rc1/2.6.22-rc1-mm1/broken-out/gregkh-driver-sysfs-allocate-inode-number-using-ida.patch
>> for the 2.6.16 -stable tree - it follows the same scheme of using s_ino to safely
>> store & retrieve the inode number of sysfs entries for use in sysfs_readdir,
>> but uses a brain-dead-simple inode nr allocator rather than ida, which would
>> bring along a lot of newer, more complex code.
>>
>> No, this doesn't guarantee uniqueness of sysfs inode numbers, but then
>> the code in -stable today doesn't either - and with this change, at least
>> it shouldn't oops.
>
> So I'm sitting here whether to commend this patch to google kernel maintainers
> for 2.6.18 backport, but I realise I don't know what it does. And I don't know
> if it fixes the reclaim-time oopses they were intermittently seeing, or if it
> fixes something else and if so what that is.
>
> Sigh. Better changelogs, please.
>
Sorry Andrew. I referenced Tejun's upstream patch in -mm which has a
nice changelog etc, and this is a backport of that, and does the same
thing in the same way and solves the same problem - but that doesn't
help if you just want to toss this message into your patch stack. Will
fix up & resend.
-Eric
-Eric
next prev parent reply other threads:[~2007-05-22 0:21 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-21 18:11 [stable] [PATCH] - fix oops in sysfs_readdir Eric Sandeen
2007-05-21 18:21 ` Chris Wright
2007-05-21 19:02 ` [stable] " Eric Sandeen
2007-05-21 22:39 ` Andrew Morton
2007-05-22 0:18 ` Eric Sandeen [this message]
2007-05-22 0:54 ` Andrew Morton
2007-05-22 1:11 ` Tejun Heo
2007-05-22 2:32 ` [stable] [PATCH] - store sysfs inode nrs in s_ino to avoid readdir oopses Eric Sandeen
2007-06-06 19:49 ` patch sysfs-store-sysfs-inode-nrs-in-s_ino-to-avoid-readdir-oopses.patch queued to -stable tree gregkh
2007-06-06 21:35 ` [stable] " Chris Wright
2007-06-06 21:36 ` Eric Sandeen
2007-06-06 22:05 ` Chris Wright
2007-06-06 22:30 ` Greg KH
2007-05-22 23:17 ` [stable] [PATCH] - fix oops in sysfs_readdir Adrian Bunk
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=465236EF.40102@redhat.com \
--to=sandeen@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=htejun@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=maneesh@in.ibm.com \
--cc=stable@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