[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20161004190717.yzisypxpuh5nufsc@thunk.org>
Date: Tue, 4 Oct 2016 15:07:17 -0400
From: Theodore Ts'o <tytso@....edu>
To: Al Viro <viro@...IV.linux.org.uk>
Cc: Jan Kara <jack@...e.cz>, Tony Lindgren <tony@...mide.com>,
Eric Biggers <ebiggers@...gle.com>,
Andreas Dilger <adilger@...ger.ca>,
Jaegeuk Kim <jaegeuk@...nel.org>, linux-ext4@...r.kernel.org,
linux-kernel@...r.kernel.org, linux-omap@...r.kernel.org
Subject: Re: Regression in next with ext4 oops
On Tue, Oct 04, 2016 at 03:59:15PM +0100, Al Viro wrote:
> Jan is wrong - we do have per-struct-file serialization for getdents()
> et.al. It might be a race between getdents() on *different* struct
> file for the same directory, but ->private_data is not a problem.
So the rb_insert_color() OOPS seems to indicate that the rbtree has
gotten corrupted, and it hangs off of private_data.
And I've just checked the ext4.git tree and I can't see any changes in
the dev branch (which I was just about to push to Linus) that would
impact the readdir path for non-encrypted directories. So if it's a
race on ->private_data I'm not sure what else might be going wrong.
Hmm... Tony, what version was the last good version where it wouldn't
reproduce for you? v4.7? Does it reproduce for you on v4.8?
Also, would you mind seeing if you can reproduce it on the dev
branch of the ext4 git tree?
git://git.kernel.org/pub/scm/linux/kernel/git/tytso/ext4.git dev
Thanks,
- Ted
--
To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists