From: syzbot <syzbot+0be4f339a8218d2a5bb1@syzkaller.appspotmail.com>
To: eraykrdg1@gmail.com, linux-kernel@vger.kernel.org,
syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [ext4?] WARNING in ext4_xattr_inode_update_ref
Date: Fri, 19 Sep 2025 16:56:02 -0700 [thread overview]
Message-ID: <68cded92.050a0220.13cd81.000c.GAE@google.com> (raw)
In-Reply-To: <CAHxJ8O9EHnwSkBNOmBOEg3GvDxcnqsQ5cURd+uG8G2EvUcXYfg@mail.gmail.com>
Hello,
syzbot has tested the proposed patch and the reproducer did not trigger any issue:
Reported-by: syzbot+0be4f339a8218d2a5bb1@syzkaller.appspotmail.com
Tested-by: syzbot+0be4f339a8218d2a5bb1@syzkaller.appspotmail.com
Tested on:
commit: cd89d487 Merge tag '6.17-rc6-smb3-client-fixes' of git..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=167ca0e2580000
kernel config: https://syzkaller.appspot.com/x/.config?x=f5b21423ca3f0a96
dashboard link: https://syzkaller.appspot.com/bug?extid=0be4f339a8218d2a5bb1
compiler: Debian clang version 20.1.8 (++20250708063551+0c9f909b7976-1~exp1~20250708183702.136), Debian LLD 20.1.8
patch: https://syzkaller.appspot.com/x/patch.diff?x=14551858580000
Note: testing is done by a robot and is best-effort only.
next parent reply other threads:[~2025-09-19 23:56 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAHxJ8O9EHnwSkBNOmBOEg3GvDxcnqsQ5cURd+uG8G2EvUcXYfg@mail.gmail.com>
2025-09-19 23:56 ` syzbot [this message]
[not found] <CAHxJ8O_w8ewga16ORMaoM8MZj_pbh02ZRV1T_z1B6i8Q=9AE6g@mail.gmail.com>
2025-09-24 19:56 ` [syzbot] [ext4?] WARNING in ext4_xattr_inode_update_ref syzbot
[not found] <CADfthj3f-mmvvm3tAWLUmtZGTKw46+eqxZhPekLA_eKLgOUG2g@mail.gmail.com>
2025-09-18 5:19 ` syzbot
[not found] <CADfthj0NZ7duGqudQRUfmE=J69+hBkb+gWKQMVrJ18hDsMUGpw@mail.gmail.com>
2025-09-18 4:20 ` syzbot
[not found] <CAHxJ8O_F5ssDpCPi48eHRY=q29odqrjnOxfvdoOd5xppdhht7A@mail.gmail.com>
2025-09-18 1:28 ` syzbot
2025-09-11 0:08 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=68cded92.050a0220.13cd81.000c.GAE@google.com \
--to=syzbot+0be4f339a8218d2a5bb1@syzkaller.appspotmail.com \
--cc=eraykrdg1@gmail.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