On Mon, Apr 18, 2016 at 03:12:47PM +0800, Huang, Ying wrote: > That is, there is same issue for T1, but no such issue for T2. > > > How reproducible it is and how certain you are that it's not there on > > the parent commit? > > The result is quite stable for tens tests for parents and the first bad > commit.
Nuts... Try vfs.git#T3, please - the only way this could cause memory corruption, AFAICS, is some really weird caller of d_add() or d_splice_alias(), passing it a dentry with bogus ->d_parent...
