From: Eryu Guan <eguan@redhat.com>
To: Miklos Szeredi <miklos@szeredi.hu>
Cc: linux-unionfs@vger.kernel.org, Miklos Szeredi <mszeredi@redhat.com>
Subject: Re: [4.13-rc1 regression] copyup crashes kernel when initializing selinux
Date: Mon, 17 Jul 2017 20:12:01 +0800 [thread overview]
Message-ID: <20170717121201.GR2478@eguan.usersys.redhat.com> (raw)
In-Reply-To: <20170717112503.GB5256@veci.piliscsaba.szeredi.hu>
On Mon, Jul 17, 2017 at 01:25:03PM +0200, Miklos Szeredi wrote:
> On Mon, Jul 17, 2017 at 05:37:41PM +0800, Eryu Guan wrote:
> > Hi all,
> >
> > I hit a kernel crash with 4.13-rc1 kernel when running fstests
> > overlay/005. And git bisect pointed first bad to this commit
> >
> > commit 09d8b586731bf589655c2ac971532c14cf272b63
> > Author: Miklos Szeredi <mszeredi@redhat.com>
> > Date: Tue Jul 4 22:03:16 2017 +0200
> >
> > ovl: move __upperdentry to ovl_inode
> >
> > Signed-off-by: Miklos Szeredi <mszeredi@redhat.com>
> >
> > inode_doinit_with_dentry wants to read the upper inode's xattr to get
> > selinux information, and ovl_xattr_get() calls ovl_dentry_real(), which
> > depends on dentry->d_inode, but d_inode is null and not initialized yet
> > at this moment.
> >
> > Mount overlay without selinux context mount option and trigger copyup
> > could reproduce the crash reliably. (The crash log I appended is from a
> > bisect run, so the kernel version is not exact 4.13-rc1.)
>
> Could you please test following patch?
This patch works for me, but I just ran overlay/005, didn't run other
tests.
Thanks,
Eryu
next prev parent reply other threads:[~2017-07-17 12:12 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-17 9:37 [4.13-rc1 regression] copyup crashes kernel when initializing selinux Eryu Guan
2017-07-17 11:25 ` Miklos Szeredi
2017-07-17 12:12 ` Eryu Guan [this message]
2017-07-17 14:42 ` Vivek Goyal
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20170717121201.GR2478@eguan.usersys.redhat.com \
--to=eguan@redhat.com \
--cc=linux-unionfs@vger.kernel.org \
--cc=miklos@szeredi.hu \
--cc=mszeredi@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox