[lkml]   [2014]   [Oct]   [25]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: fs: lockup on rename_mutex in fs/dcache.c:1035
On Sat, Oct 25, 2014 at 08:01:41PM -0700, Eric W. Biederman wrote:
> Sasha Levin <> writes:
> > Hi all,
> >
> > While fuzzing with trinity inside a KVM tools guest running the latest -next
> > kernel, I've stumbled on the following spew:
> Weird. I took a quick look and I don't see any changes in d_walk that
> in Al's tree or in Linus's kernel for years.
> Has read_seqbegin_or_lock changed somewhere?
> >From a quick reading of the code it simply isn't possible for d_walk to
> take the lock twice short of memory corruption. And the fact that the
> code has not changed in years seems to suggest it isn't the obvious
> cause of d_walk talking the rename_lock twice.

It is a fairly obvious case of d_walk() forgetting to drop rename_lock.
See upthread for analysis and (hopefully) a fix.

 \ /
  Last update: 2014-10-26 04:41    [W:0.048 / U:1.600 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site