Re: [syzbot] WARNING: kobject bug in erofs_unregister_sysfs

[Gao Xiang]

On Mon, Mar 21, 2022 at 07:55:29AM +0100, Dmitry Vyukov wrote:
> On Sun, 20 Mar 2022 at 05:19, Dongliang Mu <mudongliangabcd@xxxxxxxxx> wrote:
> >
> > On Sat, Mar 19, 2022 at 10:21 AM Muchun Song <songmuchun@xxxxxxxxxxxxx> wrote:
> > >
> > > On Sat, Mar 19, 2022 at 6:33 AM syzbot
> > > <syzbot+f05ba4652c0471416eaf@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote:
> > > >
> > > > syzbot has bisected this issue to:
> > > >
> > > > commit 2768c206f2c3e95c0e5cf2e7f846103fda7cd429
> > > > Author: Muchun Song <songmuchun@xxxxxxxxxxxxx>
> > > > Date:   Thu Mar 3 01:15:36 2022 +0000
> > > >
> > > >     mm: list_lru: allocate list_lru_one only when needed
> > > >
> > > > bisection log:  https://syzkaller.appspot.com/x/bisect.txt?x=1495694d700000
> > > > start commit:   91265a6da44d Add linux-next specific files for 20220303
> > > > git tree:       linux-next
> > > > final oops:     https://syzkaller.appspot.com/x/report.txt?x=1695694d700000
> > > > console output: https://syzkaller.appspot.com/x/log.txt?x=1295694d700000
> > > > kernel config:  https://syzkaller.appspot.com/x/.config?x=617f79440a35673a
> > > > dashboard link: https://syzkaller.appspot.com/bug?extid=f05ba4652c0471416eaf
> > > > syz repro:      https://syzkaller.appspot.com/x/repro.syz?x=137f17d9700000
> > > > C reproducer:   https://syzkaller.appspot.com/x/repro.c?x=114ebabd700000
> > > >
> > > > Reported-by: syzbot+f05ba4652c0471416eaf@xxxxxxxxxxxxxxxxxxxxxxxxx
> > > > Fixes: 2768c206f2c3 ("mm: list_lru: allocate list_lru_one only when needed")
> > >
> > > Does this patch [1] fix the issue? If yes, I am confused why the Fixes tag
> > > should be the commit 2768c206f2c3?  What am I missing here?
> >
> > Sometimes syzkaller bisection may make mistakes. Please ignore it.
> >
> > >
> > > [1] https://lore.kernel.org/r/20220315132814.12332-1-dzm91@xxxxxxxxxxx
> >
> 
> Let's tell syzbot so that it reports new bugs in future:
> 
> #syz fix: fs: erofs: add sanity check for kobject in erofs_unregister_sysfs

Thanks! The fix has been landed upstream now.

Thanks,
Gao Xiang