All of lore.kernel.org
 help / color / mirror / Atom feed
From: Gao Xiang <xiang@kernel.org>
To: Muchun Song <songmuchun@bytedance.com>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
	syzkaller-bugs@googlegroups.com,
	LKML <linux-kernel@vger.kernel.org>,
	syzbot <syzbot+f05ba4652c0471416eaf@syzkaller.appspotmail.com>,
	Andrew Morton <akpm@linux-foundation.org>,
	linux-erofs@lists.ozlabs.org
Subject: Re: [syzbot] WARNING: kobject bug in erofs_unregister_sysfs
Date: Sat, 19 Mar 2022 11:45:12 +0800	[thread overview]
Message-ID: <YjVRyIpIUN1jB8iK@debian> (raw)
In-Reply-To: <CAMZfGtWL-2+en7=FKBoPUwq1FMGYYqZCvB1jmJ7fhiQc1XX4oQ@mail.gmail.com>

On Sat, Mar 19, 2022 at 10:19:12AM +0800, Muchun Song wrote:
> On Sat, Mar 19, 2022 at 6:33 AM syzbot
> <syzbot+f05ba4652c0471416eaf@syzkaller.appspotmail.com> wrote:
> >
> > syzbot has bisected this issue to:
> >
> > commit 2768c206f2c3e95c0e5cf2e7f846103fda7cd429
> > Author: Muchun Song <songmuchun@bytedance.com>
> > 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@syzkaller.appspotmail.com
> > 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?
> 
> [1] https://lore.kernel.org/r/20220315132814.12332-1-dzm91@hust.edu.cn

I think it was an incorrect bisect so we could just ignore it.
The fix is already pending for the next merge window.

Thanks,
Gao Xiang

> 
> Thanks.

WARNING: multiple messages have this Message-ID (diff)
From: Gao Xiang <xiang@kernel.org>
To: Muchun Song <songmuchun@bytedance.com>
Cc: syzbot <syzbot+f05ba4652c0471416eaf@syzkaller.appspotmail.com>,
	Andrew Morton <akpm@linux-foundation.org>,
	chao@kernel.org, linux-erofs@lists.ozlabs.org,
	LKML <linux-kernel@vger.kernel.org>,
	Stephen Rothwell <sfr@canb.auug.org.au>,
	syzkaller-bugs@googlegroups.com, xiang@kernel.org
Subject: Re: [syzbot] WARNING: kobject bug in erofs_unregister_sysfs
Date: Sat, 19 Mar 2022 11:45:12 +0800	[thread overview]
Message-ID: <YjVRyIpIUN1jB8iK@debian> (raw)
In-Reply-To: <CAMZfGtWL-2+en7=FKBoPUwq1FMGYYqZCvB1jmJ7fhiQc1XX4oQ@mail.gmail.com>

On Sat, Mar 19, 2022 at 10:19:12AM +0800, Muchun Song wrote:
> On Sat, Mar 19, 2022 at 6:33 AM syzbot
> <syzbot+f05ba4652c0471416eaf@syzkaller.appspotmail.com> wrote:
> >
> > syzbot has bisected this issue to:
> >
> > commit 2768c206f2c3e95c0e5cf2e7f846103fda7cd429
> > Author: Muchun Song <songmuchun@bytedance.com>
> > 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@syzkaller.appspotmail.com
> > 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?
> 
> [1] https://lore.kernel.org/r/20220315132814.12332-1-dzm91@hust.edu.cn

I think it was an incorrect bisect so we could just ignore it.
The fix is already pending for the next merge window.

Thanks,
Gao Xiang

> 
> Thanks.

  reply	other threads:[~2022-03-19  3:46 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-18 16:39 [syzbot] WARNING: kobject bug in erofs_unregister_sysfs syzbot
2022-03-18 18:02 ` Gao Xiang
2022-03-18 18:02   ` Gao Xiang
2022-03-18 18:52   ` syzbot
2022-03-18 22:33 ` syzbot
2022-03-19  2:19   ` Muchun Song
2022-03-19  2:19     ` Muchun Song
2022-03-19  3:45     ` Gao Xiang [this message]
2022-03-19  3:45       ` Gao Xiang
2022-03-20  4:19     ` Dongliang Mu
2022-03-20  4:19       ` Dongliang Mu
2022-03-21  6:55       ` Dmitry Vyukov via Linux-erofs
2022-03-21  6:55         ` Dmitry Vyukov
2022-03-23  1:54         ` Gao Xiang
2022-03-23  1:54           ` Gao Xiang

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=YjVRyIpIUN1jB8iK@debian \
    --to=xiang@kernel.org \
    --cc=akpm@linux-foundation.org \
    --cc=linux-erofs@lists.ozlabs.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sfr@canb.auug.org.au \
    --cc=songmuchun@bytedance.com \
    --cc=syzbot+f05ba4652c0471416eaf@syzkaller.appspotmail.com \
    --cc=syzkaller-bugs@googlegroups.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.