public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: syzbot <syzbot+2e6fb1f89ce5e13cd02d@syzkaller.appspotmail.com>
To: gianf.trad@gmail.com, linux-kernel@vger.kernel.org,
	 syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [hfs?] KMSAN: uninit-value in hfs_free_fork
Date: Tue, 22 Oct 2024 15:40:03 -0700	[thread overview]
Message-ID: <671829c3.050a0220.10f4f4.0182.GAE@google.com> (raw)
In-Reply-To: <49b1ba71-1c1e-43e9-a012-42c17f0aad85@gmail.com>

Hello,

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

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

Tested on:

commit:         c2ee9f59 KVM: selftests: Fix build on on non-x86 archi..
git tree:       upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=12f4a640580000
kernel config:  https://syzkaller.appspot.com/x/.config?x=fa3d7fc2fd6ea40d
dashboard link: https://syzkaller.appspot.com/bug?extid=2e6fb1f89ce5e13cd02d
compiler:       Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40
patch:          https://syzkaller.appspot.com/x/patch.diff?x=10eb8287980000

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

  reply	other threads:[~2024-10-22 22:40 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <41a67fa0-52c7-4089-8cb1-3d3d622cbcff@gmail.com>
2024-10-22 22:07 ` [syzbot] [hfs?] KMSAN: uninit-value in hfs_free_fork syzbot
2024-10-22 22:11   ` Gianfranco Trad
2024-10-22 22:40     ` syzbot [this message]
     [not found] <6f129270-4c3c-454b-831b-4fe2f5597bc7@gmail.com>
2024-11-11 20:49 ` syzbot
     [not found] <429d2bea-ef68-4130-bb8a-0fb5fd38663c@gmail.com>
2024-11-11 20:21 ` syzbot
     [not found] <18374947-f71e-4f71-b097-f06eb0699bfa@gmail.com>
2024-11-11 20:21 ` syzbot
2024-05-06  7:01 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=671829c3.050a0220.10f4f4.0182.GAE@google.com \
    --to=syzbot+2e6fb1f89ce5e13cd02d@syzkaller.appspotmail.com \
    --cc=gianf.trad@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