On Tue, May 29, 2012 at 05:21:44PM +0900, Greg KH wrote: > On Mon, May 28, 2012 at 01:33:42PM -0400, Theodore Ts'o wrote: > > If we rmdir a directory which is a hard link to '.', we will deadlock > > trying to grab the directory's i_mutex. Check for this condition and > > return EINVAL, which is what we return if the user attempts to rmdir > > "/foo/bar/." > > > > Signed-off-by: "Theodore Ts'o" <tytso@xxxxxxx> > > --- > > fs/namei.c | 11 +++++++++++ > > 1 file changed, 11 insertions(+) > > Any reason why you didn't also tag this for the stable kernel releases? Because I was sending it out for comment; I wanted to get Al's opinion how to handle whether we needed to inform the low-level file system about the corruption. I should have added an RFC to the subject line, sorry. Andrea's solution of detecting the corruption is lookup seems like the right answer, so at this point, I'll remove the XXX comment, and add the unlikely() annotation to the if statement, and resubmit with a Cc: stable. - Ted -- To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
