linux-kernel - Re: [PATCH 2/2] Fix i_state of inode is changed after the inode is freed [try #2]

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] [thread-next>] [day] [month] [year] [list]

Date:	Thu, 31 Aug 2006 13:19:02 +1000
From:	Nathan Scott <nathans@....com>
To:	Masayuki Saito <m-saito@...s.nec.co.jp>
Cc:	David Chinner <dgc@....com>, xfs@....sgi.com,
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH 2/2] Fix i_state of inode is changed after the inode is freed [try #2]

On Thu, Aug 31, 2006 at 11:44:23AM +0900, Masayuki Saito wrote:
> Hi, Nathan
> 
> Are the patches going to be merged?

Yep, they're queued up for 2.6.19.  Since it was a race found
only on testing with a ramdisk (iirc) it didn't really seem to
me like they needed to be rushed through for a 2.6.18-rc.  The
race has also been there for the entire lifetime of the Linux
XFS port... so, not urgent (and not risk free either).

cheers.

-- 
Nathan
-
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/