From: syzbot <syzbot+13e8cd4926977f8337b6@syzkaller.appspotmail.com>
To: aha310510@gmail.com, linux-kernel@vger.kernel.org,
syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [jfs?] UBSAN: shift-out-of-bounds in extAlloc (2)
Date: Fri, 31 May 2024 11:18:03 -0700 [thread overview]
Message-ID: <0000000000001ad3710619c4018d@google.com> (raw)
In-Reply-To: <20240531110652.8845-1-aha310510@gmail.com>
Hello,
syzbot has tested the proposed patch and the reproducer did not trigger any issue:
Reported-and-tested-by: syzbot+13e8cd4926977f8337b6@syzkaller.appspotmail.com
Tested on:
commit: 4a4be1ad Revert "vfs: Delete the associated dentry whe..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=14f8f016980000
kernel config: https://syzkaller.appspot.com/x/.config?x=b9016f104992d69c
dashboard link: https://syzkaller.appspot.com/bug?extid=13e8cd4926977f8337b6
compiler: Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40
patch: https://syzkaller.appspot.com/x/patch.diff?x=1001cc4a980000
Note: testing is done by a robot and is best-effort only.
next prev parent reply other threads:[~2024-05-31 18:18 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-03 13:40 [syzbot] [jfs?] UBSAN: shift-out-of-bounds in extAlloc (2) syzbot
2024-05-31 11:06 ` Jeongjun Park
2024-05-31 18:18 ` syzbot [this message]
2024-06-01 0:29 ` Changheon LEE
2024-06-01 2:56 ` Jeongjun Park
2024-06-01 3:00 ` Jeongjun Park
2024-06-01 3:31 ` syzbot
2025-09-28 2:54 ` Forwarded: " syzbot
2026-04-17 10:12 ` Forwarded: [PATCH] jfs: validate db_maxfreebud in extBalloc to prevent syzbot
2026-04-17 16:20 ` Forwarded: Re: [syzbot] UBSAN: shift-out-of-bounds in extBalloc syzbot
[not found] <87zfafi8w9.fsf@gmail.com>
2025-09-28 3:16 ` [syzbot] [jfs?] UBSAN: shift-out-of-bounds in extAlloc (2) syzbot
[not found] <20260417101220.2490685-1-tristmd@gmail.com>
2026-04-17 11:01 ` syzbot
[not found] <177644283705.3787593.12153382858474209734@talencesecurity.com>
2026-04-17 17:48 ` 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=0000000000001ad3710619c4018d@google.com \
--to=syzbot+13e8cd4926977f8337b6@syzkaller.appspotmail.com \
--cc=aha310510@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 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.