mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: syzbot <syzbot+0ea5108a1f5fb4fcc2d8@syzkaller.appspotmail.com>
To: agruenba@redhat.com, linux-kernel@vger.kernel.org,
	 syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [gfs2?] WARNING in filename_mkdirat
Date: Mon, 23 Feb 2026 04:08:02 -0800	[thread overview]
Message-ID: <699c4322.050a0220.1876f9.0003.GAE@google.com> (raw)
In-Reply-To: <CAHc6FU6++PN7ZADKHtTc8Ai6_ODTEs6-8mu5Ot_tqXfTG0DufQ@mail.gmail.com>

Hello,

syzbot has tested the proposed patch and the reproducer did not trigger any issue:

Reported-by: syzbot+0ea5108a1f5fb4fcc2d8@syzkaller.appspotmail.com
Tested-by: syzbot+0ea5108a1f5fb4fcc2d8@syzkaller.appspotmail.com

Tested on:

commit:         2ff7cf7e gfs2: Call unlock_new_inode before d_instanti..
git tree:       git://git.kernel.org/pub/scm/linux/kernel/git/gfs2/linux-gfs2.git for-next
console output: https://syzkaller.appspot.com/x/log.txt?x=15c5395a580000
kernel config:  https://syzkaller.appspot.com/x/.config?x=1b7a263e05047155
dashboard link: https://syzkaller.appspot.com/bug?extid=0ea5108a1f5fb4fcc2d8
compiler:       Debian clang version 21.1.8 (++20251221033036+2078da43e25a-1~exp1~20251221153213.50), Debian LLD 21.1.8

Note: no patches were applied.
Note: testing is done by a robot and is best-effort only.

       reply	other threads:[~2026-02-23 12:08 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CAHc6FU6++PN7ZADKHtTc8Ai6_ODTEs6-8mu5Ot_tqXfTG0DufQ@mail.gmail.com>
2026-02-23 12:08 ` syzbot [this message]
2026-02-17  0:30 syzbot
2026-02-17  8:15 ` Christian Brauner
2026-02-17  9:12   ` NeilBrown
2026-02-17 22:18     ` NeilBrown
2026-02-19  8:09       ` Christian Brauner
2026-02-19 21:45         ` NeilBrown
2026-02-23 15:36           ` Andreas Gruenbacher
2026-02-19  7:26 ` syzbot

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=699c4322.050a0220.1876f9.0003.GAE@google.com \
    --to=syzbot+0ea5108a1f5fb4fcc2d8@syzkaller.appspotmail.com \
    --cc=agruenba@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --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

Powered by JetHome