public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: syzbot <syzbot+fe2a25dae02a207717a0@syzkaller.appspotmail.com>
To: dmantipov@yandex.ru, linux-kernel@vger.kernel.org,
	 syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [ext4?] kernel BUG in ext4_write_inline_data (2)
Date: Thu, 21 Nov 2024 05:10:02 -0800	[thread overview]
Message-ID: <673f312a.050a0220.3c9d61.0171.GAE@google.com> (raw)
In-Reply-To: <20241121124343.VLW_9%dmantipov@yandex.ru>

Hello,

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

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

Tested on:

commit:         43fb83c1 Merge tag 'soc-arm-6.13' of git://git.kernel...
git tree:       https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
console output: https://syzkaller.appspot.com/x/log.txt?x=12c05930580000
kernel config:  https://syzkaller.appspot.com/x/.config?x=1638cad79464dac0
dashboard link: https://syzkaller.appspot.com/bug?extid=fe2a25dae02a207717a0
compiler:       gcc (Debian 12.2.0-14) 12.2.0, GNU ld (GNU Binutils for Debian) 2.40
patch:          https://syzkaller.appspot.com/x/patch.diff?x=149beb78580000

Note: testing is done by a robot and is best-effort only.

       reply	other threads:[~2024-11-21 13:10 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20241121124343.VLW_9%dmantipov@yandex.ru>
2024-11-21 13:10 ` syzbot [this message]
     [not found] <CAPXz4EOcrGyLkp9XGn8-XgzfuebuW5=AdR72hP8Qf2hK0DrHcw@mail.gmail.com>
2024-11-22 17:13 ` [syzbot] [ext4?] kernel BUG in ext4_write_inline_data (2) syzbot
2024-11-22 18:33   ` Nicolas Bretz
2024-11-22 18:59     ` syzbot
2024-11-22 19:20       ` Nicolas Bretz
2024-11-22 20:09         ` syzbot
     [not found] <CAPXz4ENUgZteGDF3w3iFLA-Rdbfsm2e4XUYcfdHRgwATk5mF9Q@mail.gmail.com>
2024-11-22 16:21 ` syzbot
2024-11-21  9:00 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=673f312a.050a0220.3c9d61.0171.GAE@google.com \
    --to=syzbot+fe2a25dae02a207717a0@syzkaller.appspotmail.com \
    --cc=dmantipov@yandex.ru \
    --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