From: syzbot <syzbot+18df508cf00a0598d9a6@syzkaller.appspotmail.com>
To: linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com,
wojciech.gladysz@infogain.com
Subject: Re: [syzbot] [ext4?] general protection fault in __block_commit_write
Date: Mon, 01 Jul 2024 04:32:02 -0700 [thread overview]
Message-ID: <0000000000002ad6e4061c2df2a4@google.com> (raw)
In-Reply-To: <20240701084553.24215-1-wojciech.gladysz@infogain.com>
Hello,
syzbot has tested the proposed patch and the reproducer did not trigger any issue:
Reported-and-tested-by: syzbot+18df508cf00a0598d9a6@syzkaller.appspotmail.com
Tested on:
commit: 22a40d14 Linux 6.10-rc6
git tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
console output: https://syzkaller.appspot.com/x/log.txt?x=1508f869980000
kernel config: https://syzkaller.appspot.com/x/.config?x=f85e95b525c28b48
dashboard link: https://syzkaller.appspot.com/bug?extid=18df508cf00a0598d9a6
compiler: Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40
userspace arch: arm64
patch: https://syzkaller.appspot.com/x/patch.diff?x=110d6885980000
Note: testing is done by a robot and is best-effort only.
next parent reply other threads:[~2024-07-01 11:32 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240701084553.24215-1-wojciech.gladysz@infogain.com>
2024-07-01 11:32 ` syzbot [this message]
[not found] <20240701084542.24151-1-wojciech.gladysz@infogain.com>
2024-07-01 11:46 ` [syzbot] [ext4?] general protection fault in __block_commit_write syzbot
[not found] <20240701083435.19182-1-wojciech.gladysz@infogain.com>
2024-07-01 11:18 ` syzbot
[not found] <20240701082944.17441-1-wojciech.gladysz@infogain.com>
2024-07-01 8:54 ` syzbot
2024-02-05 9:01 syzbot
2024-05-20 1:52 ` 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=0000000000002ad6e4061c2df2a4@google.com \
--to=syzbot+18df508cf00a0598d9a6@syzkaller.appspotmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=syzkaller-bugs@googlegroups.com \
--cc=wojciech.gladysz@infogain.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