From: Chris Wright <chrisw@sous-sol.org>
To: Eric Sandeen <sandeen@sandeen.net>
Cc: Chris Wright <chrisw@sous-sol.org>,
gregkh@suse.de, akpm@linux-foundation.org, htejun@gmail.com,
linux-kernel@vger.kernel.org, maneesh@in.ibm.com,
sandeen@redhat.com, stable@kernel.org
Subject: Re: [stable] patch sysfs-store-sysfs-inode-nrs-in-s_ino-to-avoid-readdir-oopses.patch queued to -stable tree
Date: Wed, 6 Jun 2007 15:05:04 -0700 [thread overview]
Message-ID: <20070606220504.GT3723@sequoia.sous-sol.org> (raw)
In-Reply-To: <466728D6.30200@sandeen.net>
* Eric Sandeen (sandeen@sandeen.net) wrote:
> Well, my backport of Tejun's patch explicitly doesn't use ida for just
> that reason...
>
> It uses a simple counter instead (which may give dup inode numbers, but
> I think we have that today, and at least this shouldn't oops...)
Right, my point is the source of the backport is in -mm for maybe as
long as 6 weeks but not in Linus' tree. I s'pose it's chicken and egg
for the ida code. I'd prefer to see your patch upstream, and Tejun's
code becomes the ida code plus conversion of the simple counter to ida
at some later point in time.
next prev parent reply other threads:[~2007-06-06 22:05 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
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 [this message]
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=20070606220504.GT3723@sequoia.sous-sol.org \
--to=chrisw@sous-sol.org \
--cc=akpm@linux-foundation.org \
--cc=gregkh@suse.de \
--cc=htejun@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=maneesh@in.ibm.com \
--cc=sandeen@redhat.com \
--cc=sandeen@sandeen.net \
--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
Powered by JetHome