From: syzbot <syzbot+544248a761451c0df72f@syzkaller.appspotmail.com>
To: adilger.kernel@dilger.ca, linux-ext4@vger.kernel.org,
linux-kernel@vger.kernel.org, moonhee.lee.ca@gmail.com,
syzkaller-bugs@googlegroups.com, tytso@mit.edu
Subject: Re: [syzbot] [ext4?] kernel BUG in ext4_update_inline_data
Date: Thu, 10 Jul 2025 01:23:03 -0700 [thread overview]
Message-ID: <686f7867.050a0220.385921.002f.GAE@google.com> (raw)
In-Reply-To: <CAF3JpA7a0ExYEJ8_c7v7evKsV83s+_p7qUoH9uiYZLPxT_Md6g@mail.gmail.com>
Hello,
syzbot has tested the proposed patch and the reproducer did not trigger any issue:
Reported-by: syzbot+544248a761451c0df72f@syzkaller.appspotmail.com
Tested-by: syzbot+544248a761451c0df72f@syzkaller.appspotmail.com
Tested on:
commit: 8c2e52eb eventpoll: don't decrement ep refcount while ..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=14ff7582580000
kernel config: https://syzkaller.appspot.com/x/.config?x=b309c907eaab29da
dashboard link: https://syzkaller.appspot.com/bug?extid=544248a761451c0df72f
compiler: Debian clang version 20.1.7 (++20250616065708+6146a88f6049-1~exp1~20250616065826.132), Debian LLD 20.1.7
patch: https://syzkaller.appspot.com/x/patch.diff?x=15ef7582580000
Note: testing is done by a robot and is best-effort only.
next prev parent reply other threads:[~2025-07-10 8:23 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-10 8:01 [syzbot] [ext4?] kernel BUG in ext4_update_inline_data Moon Hee Lee
2025-07-10 8:23 ` syzbot [this message]
2025-07-17 14:59 ` [PATCH] ext4: do not BUG when INLINE_DATA_FL lacks system.data xattr Theodore Ts'o
2025-07-17 16:59 ` Moon Hee Lee
2025-07-17 19:53 ` Moon Hee Lee
2025-07-18 1:05 ` Theodore Ts'o
2025-07-21 12:49 ` Jan Kara
2025-07-21 13:51 ` Theodore Ts'o
2025-07-18 11:11 ` [PATCH -v2] " Theodore Ts'o
-- strict thread matches above, loose matches on Subject: below --
2025-07-07 16:32 [syzbot] [ext4?] kernel BUG in ext4_update_inline_data 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=686f7867.050a0220.385921.002f.GAE@google.com \
--to=syzbot+544248a761451c0df72f@syzkaller.appspotmail.com \
--cc=adilger.kernel@dilger.ca \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=moonhee.lee.ca@gmail.com \
--cc=syzkaller-bugs@googlegroups.com \
--cc=tytso@mit.edu \
/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.