From: syzbot <syzbot+39b2fb0f2638669008ec@syzkaller.appspotmail.com>
To: almaz.alexandrovich@paragon-software.com,
andrewjballance@gmail.com,
linux-kernel-mentees@lists.linuxfoundation.org,
linux-kernel@vger.kernel.org, ntfs3@lists.linux.dev,
skhan@linuxfoundation.org, syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [ntfs3?] UBSAN: array-index-out-of-bounds in decompress_lznt
Date: Wed, 15 May 2024 05:59:03 -0700 [thread overview]
Message-ID: <000000000000d50ab606187dae67@google.com> (raw)
In-Reply-To: <20240515123946.874688-1-andrewjballance@gmail.com>
Hello,
syzbot has tested the proposed patch and the reproducer did not trigger any issue:
Reported-and-tested-by: syzbot+39b2fb0f2638669008ec@syzkaller.appspotmail.com
Tested on:
commit: 1b294a1f Merge tag 'net-next-6.10' of git://git.kernel..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=15998648980000
kernel config: https://syzkaller.appspot.com/x/.config?x=c0cd0c5dbf8ea592
dashboard link: https://syzkaller.appspot.com/bug?extid=39b2fb0f2638669008ec
compiler: Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40
patch: https://syzkaller.appspot.com/x/patch.diff?x=115b78f0980000
Note: testing is done by a robot and is best-effort only.
next prev parent reply other threads:[~2024-05-15 12:59 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-14 16:19 [syzbot] [ntfs3?] UBSAN: array-index-out-of-bounds in decompress_lznt syzbot
2024-05-15 12:38 ` [PATCH] ntfs3: check if more than chunk-size bytes are written Andrew Ballance
2024-05-15 12:59 ` syzbot [this message]
2024-07-01 21:55 ` [syzbot] test syzbot
2024-08-23 16:04 ` [syzbot] UBSAN: array-index-out-of-bounds in decompress_lznt syzbot
2026-04-17 10:12 ` Forwarded: [PATCH] ntfs3: fix " syzbot
2026-04-17 16:20 ` Forwarded: Re: [syzbot] KASAN: slab-out-of-bounds " syzbot
[not found] <CA+LQOUeqBUoayxCX+Qkmf5NrEepftimrTySacg=G==F-V=nvvQ@mail.gmail.com>
2024-07-01 22:35 ` [syzbot] [ntfs3?] UBSAN: array-index-out-of-bounds " syzbot
[not found] <199d972e9c5748a3b18a88feff01aa0b@paragon-software.com>
2024-08-23 17:04 ` syzbot
[not found] <20260417101207.2489867-1-tristmd@gmail.com>
2026-04-17 10:46 ` syzbot
[not found] <177644284372.3787959.6249375020063212098@talencesecurity.com>
2026-04-17 17:53 ` 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=000000000000d50ab606187dae67@google.com \
--to=syzbot+39b2fb0f2638669008ec@syzkaller.appspotmail.com \
--cc=almaz.alexandrovich@paragon-software.com \
--cc=andrewjballance@gmail.com \
--cc=linux-kernel-mentees@lists.linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ntfs3@lists.linux.dev \
--cc=skhan@linuxfoundation.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 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.