From: Aleksandr Nogikh <nogikh@google.com>
To: syzbot <syzbot+eba014ac93ef29f83dc8@syzkaller.appspotmail.com>
Cc: akpm@linux-foundation.org,
almaz.alexandrovich@paragon-software.com, davem@davemloft.net,
hughd@google.com, jiri@nvidia.com, kuba@kernel.org,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-mm@kvack.org, ntfs3@lists.linux.dev,
syzkaller-bugs@googlegroups.com, viro@zeniv.linux.org.uk
Subject: Re: [syzbot] [ntfs3?] WARNING in walk_component
Date: Thu, 13 Jul 2023 10:31:55 +0200 [thread overview]
Message-ID: <CANp29Y7LG7szcmLzfjNAZRpitQwn6Yh-h7zPk+demObAwuxwZw@mail.gmail.com> (raw)
In-Reply-To: <000000000000a5d5ab060055215c@google.com>
On Thu, Jul 13, 2023 at 4:31 AM syzbot
<syzbot+eba014ac93ef29f83dc8@syzkaller.appspotmail.com> wrote:
>
> syzbot suspects this issue was fixed by commit:
>
> commit d772781964415c63759572b917e21c4f7ec08d9f
> Author: Jakub Kicinski <kuba@kernel.org>
> Date: Fri Jan 6 06:33:54 2023 +0000
>
> devlink: bump the instance index directly when iterating
>
> bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=12801432a80000
> start commit: f3e8416619ce Merge tag 'soc-fixes-6.1-5' of git://git.kern..
> git tree: upstream
> kernel config: https://syzkaller.appspot.com/x/.config?x=b83f3e90d74765ea
> dashboard link: https://syzkaller.appspot.com/bug?extid=eba014ac93ef29f83dc8
> syz repro: https://syzkaller.appspot.com/x/repro.syz?x=117d216b880000
>
> If the result looks correct, please mark the issue as fixed by replying with:
>
> #syz fix: devlink: bump the instance index directly when iterating
That commit fixes a second problem triggerable by the same reproducer
-- "INFO: rcu detected stall", but it is not related to the original
"WARNING in walk_component" crash.
>
> For information about bisection process see: https://goo.gl/tpsmEJ#bisection
>
> --
prev parent reply other threads:[~2023-07-13 8:32 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <000000000000fd3bbe05efb0d1fd@google.com>
2023-01-06 16:15 ` [syzbot] [vfs?] [ntfs3?] [tmpfs?] WARNING in walk_component syzbot
2023-01-20 20:43 ` syzbot
2023-07-13 2:31 ` [syzbot] [ntfs3?] " syzbot
2023-07-13 8:31 ` Aleksandr Nogikh [this message]
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=CANp29Y7LG7szcmLzfjNAZRpitQwn6Yh-h7zPk+demObAwuxwZw@mail.gmail.com \
--to=nogikh@google.com \
--cc=akpm@linux-foundation.org \
--cc=almaz.alexandrovich@paragon-software.com \
--cc=davem@davemloft.net \
--cc=hughd@google.com \
--cc=jiri@nvidia.com \
--cc=kuba@kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=ntfs3@lists.linux.dev \
--cc=syzbot+eba014ac93ef29f83dc8@syzkaller.appspotmail.com \
--cc=syzkaller-bugs@googlegroups.com \
--cc=viro@zeniv.linux.org.uk \
/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;
as well as URLs for NNTP newsgroup(s).