linux-kernel - Re: [stable] patch sysfs-store-sysfs-inode-nrs-in-s_ino-to-avoid-readdir-oopses.patch queued to -stable tree

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Date:	Wed, 6 Jun 2007 15:30:31 -0700
From:	Greg KH <greg@...ah.com>
To:	Eric Sandeen <sandeen@...deen.net>
Cc:	Chris Wright <chrisw@...s-sol.org>, sandeen@...hat.com,
	htejun@...il.com, gregkh@...e.de, linux-kernel@...r.kernel.org,
	maneesh@...ibm.com, akpm@...ux-foundation.org, stable@...nel.org
Subject: Re: [stable] patch
	sysfs-store-sysfs-inode-nrs-in-s_ino-to-avoid-readdir-oopses.patch
	queued to -stable tree

On Wed, Jun 06, 2007 at 04:36:22PM -0500, Eric Sandeen wrote:
> Chris Wright wrote:
> > * gregkh@...e.de (gregkh@...e.de) wrote:
> >> From: Eric Sandeen <sandeen@...deen.net>
> >> Subject: sysfs: store sysfs inode nrs in s_ino to avoid readdir oopses
> >>
> >> Backport of
> >> 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
> >>
> > 
> > I didn't put this into -stable queue because the ida version is not
> > upstream yet, so I don't think it's appropriate to backport it at this
> > point in time.
> 
> 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...)

Ok, I'll pull it out as the number of people really seeing this in the
wild is so small that it's not worth it.

thanks,

greg k-h
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/