From: David Hildenbrand <david@redhat.com>
To: Aleksandr Nogikh <nogikh@google.com>
Cc: syzbot <syzbot+619c487ed60780dab217@syzkaller.appspotmail.com>,
akpm@linux-foundation.org, linux-kernel@vger.kernel.org,
linux-mm@kvack.org, linux-next@vger.kernel.org,
sfr@canb.auug.org.au, syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [mm?] linux-next test error: kernel BUG in folio_add_new_anon_rmap
Date: Fri, 11 Oct 2024 12:11:50 +0200 [thread overview]
Message-ID: <bc1358e8-438a-4385-8bde-8e6a785f6eeb@redhat.com> (raw)
In-Reply-To: <CANp29Y5VG=yj1yFgQ+Co_1E+On_F8147s727ynKyuJXoaRQG3w@mail.gmail.com>
On 11.10.24 12:05, Aleksandr Nogikh wrote:
> Hi David,
>
> On Tue, Oct 8, 2024 at 3:11 PM David Hildenbrand <david@redhat.com> wrote:
>>
>> On 08.10.24 08:51, syzbot wrote:
>>> Hello,
>>>
>>> syzbot found the following issue on:
> < ... >
>>>
>>
>> #syz fix: mm-add-pageanonnotksm-fix
>
> Just curious: this is not the commit title that will be preserved when
> the commit reaches the torvalds tree, right?
No, the fixup patch is currently in mm-unstable and will be squashed
into the responsible commit once Andrew moves it to mm-stable. So
neither commit ID nor subject are final.
>
> Syzbot uses commit titles to track which fuzzed kernel trees have
> received each bug fix, so in this case the bot will become very
> confused. If the final title is known, it's better to use that in the
> syz fix command.
That's unfortunate, but that's the way linux-next works :/
--
Cheers,
David / dhildenb
prev parent reply other threads:[~2024-10-11 10:11 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-08 6:51 syzbot
2024-10-08 13:11 ` David Hildenbrand
2024-10-11 10:05 ` Aleksandr Nogikh
2024-10-11 10:11 ` David Hildenbrand [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=bc1358e8-438a-4385-8bde-8e6a785f6eeb@redhat.com \
--to=david@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-next@vger.kernel.org \
--cc=nogikh@google.com \
--cc=sfr@canb.auug.org.au \
--cc=syzbot+619c487ed60780dab217@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox