public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: syzbot <syzbot+24ac24ff58dc5b0d26b9@syzkaller.appspotmail.com>
To: linux-kernel@vger.kernel.org, lizhi.xu@windriver.com,
	 syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [squashfs?] KMSAN: uninit-value in pick_link
Date: Thu, 01 Aug 2024 08:11:05 -0700	[thread overview]
Message-ID: <000000000000ac1d11061ea09e68@google.com> (raw)
In-Reply-To: <20240801143944.78059-1-lizhi.xu@windriver.com>

Hello,

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

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

Tested on:

commit:         2f8c4f50 Merge tag 'auxdisplay-for-v6.11-tag1' of git:..
git tree:       git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
console output: https://syzkaller.appspot.com/x/log.txt?x=1121afad980000
kernel config:  https://syzkaller.appspot.com/x/.config?x=ea3a063e5f96c3d6
dashboard link: https://syzkaller.appspot.com/bug?extid=24ac24ff58dc5b0d26b9
compiler:       Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40
patch:          https://syzkaller.appspot.com/x/patch.diff?x=12f6f94b980000

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

       reply	other threads:[~2024-08-01 15:11 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20240801143944.78059-1-lizhi.xu@windriver.com>
2024-08-01 15:11 ` syzbot [this message]
     [not found] <20240803031347.1275196-1-lizhi.xu@windriver.com>
2024-08-03  4:09 ` [syzbot] [squashfs?] KMSAN: uninit-value in pick_link syzbot
     [not found] <20240803030358.1213065-1-lizhi.xu@windriver.com>
2024-08-03  3:41 ` syzbot
     [not found] <20240802020037.976956-1-lizhi.xu@windriver.com>
2024-08-02  2:29 ` syzbot
     [not found] <20240802010252.214842-1-lizhi.xu@windriver.com>
2024-08-02  1:33 ` syzbot
     [not found] <20240801140831.4016416-1-lizhi.xu@windriver.com>
2024-08-01 14:32 ` syzbot
     [not found] <20240801130611.3460940-1-lizhi.xu@windriver.com>
2024-08-01 13:38 ` syzbot
     [not found] <20240801120853.2962357-1-lizhi.xu@windriver.com>
2024-08-01 12:42 ` syzbot
     [not found] <20240801092733.1243313-1-lizhi.xu@windriver.com>
2024-08-01 11:44 ` syzbot
     [not found] <20240801090658.1894596-1-lizhi.xu@windriver.com>
2024-08-01 11:21 ` syzbot
     [not found] <20240801012343.412607-1-lizhi.xu@windriver.com>
2024-08-01  1:55 ` syzbot
2024-07-31  8:12 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=000000000000ac1d11061ea09e68@google.com \
    --to=syzbot+24ac24ff58dc5b0d26b9@syzkaller.appspotmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lizhi.xu@windriver.com \
    --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