[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <YoRS0L0ywSZkflq7@zeniv-ca.linux.org.uk>
Date: Wed, 18 May 2022 01:58:40 +0000
From: Al Viro <viro@...iv.linux.org.uk>
To: syzbot <syzbot+5b1e53987f858500ec00@...kaller.appspotmail.com>
Cc: hdanton@...a.com, linux-kernel@...r.kernel.org,
syzkaller-bugs@...glegroups.com
Subject: Re: [syzbot] WARNING in mntput_no_expire (3)
On Wed, May 18, 2022 at 01:10:20AM +0000, Al Viro wrote:
> On Wed, May 18, 2022 at 12:59:46AM +0000, Al Viro wrote:
> > On Tue, May 17, 2022 at 10:58:15PM +0000, Al Viro wrote:
> > > On Tue, May 17, 2022 at 03:49:07PM -0700, syzbot wrote:
> > > > Hello,
> > > >
> > > > syzbot has tested the proposed patch but the reproducer is still triggering an issue:
> > > > WARNING in mntput_no_expire
> > >
> > > Obvious question: which filesystem it is?
> >
> > FWIW, can't reproduce here - at least not with C reproducer +
> > -rc7^ kernel + .config from report + debian kvm image (bullseye,
> > with systemd shite replaced with sysvinit, which might be relevant).
> >
> > In case systemd-specific braindamage is needed to reproduce it...
> > Hell knows; at least mount --make-rshared / doesn't seem to suffice.
>
> ... doesn't reproduce with genuine systemd either. FWIW, 4-way SMP
> setup here.
OK, reproduced...
Powered by blists - more mailing lists