Re: [PATCH] dcache: ensure d_flags & d_inode are consistent in lookup_fast()

On Fri, Apr 19, 2019 at 04:48:10PM +0800, Hou Tao wrote: > The root cause is the inconsistency between d_flags & d_inode > during the REF-walk in lookup_fast(): d_is_negative(dentry) > returns false, but d_backing_inode() still returns a NULL pointer. > > The RCU-walk path in lookup_fast() uses d

Re: [PATCH] dcache: ensure d_flags & d_inode are consistent in lookup_fast()

ping ? On 2019/4/19 16:48, Hou Tao wrote: > After extending the size of dentry from 192-bytes to 208-bytes > under aarch64, we got oops during the running of xfstests generic/429: > > Unable to handle kernel NULL pointer dereference at virtual address > 0002 > CPU: 3 PID: 2725 Co

[PATCH] dcache: ensure d_flags & d_inode are consistent in lookup_fast()

After extending the size of dentry from 192-bytes to 208-bytes under aarch64, we got oops during the running of xfstests generic/429: Unable to handle kernel NULL pointer dereference at virtual address 0002 CPU: 3 PID: 2725 Comm: t_encrypted_d_r Tainted: G D 5.1.0-r