All of lore.kernel.org
 help / color / mirror / Atom feed
From: syzbot <syzbot+4b717071f1eecb2972df@syzkaller.appspotmail.com>
To: hsukrut3@gmail.com, linux-kernel@vger.kernel.org,
	 syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [jfs?] UBSAN: shift-out-of-bounds in dbAllocAG (3)
Date: Fri, 17 Oct 2025 12:46:03 -0700	[thread overview]
Message-ID: <68f29cfb.050a0220.1186a4.0519.GAE@google.com> (raw)
In-Reply-To: <20251017192527.214711-1-hsukrut3@gmail.com>

Hello,

syzbot tried to test the proposed patch but the build/boot failed:

fs/jfs/jfs_dmap.c:1375:27: error: expected ')'


Tested on:

commit:         6f3b6e91 Merge tag 'io_uring-6.18-20251016' of git://g..
git tree:       upstream
kernel config:  https://syzkaller.appspot.com/x/.config?x=af9170887d81dea1
dashboard link: https://syzkaller.appspot.com/bug?extid=4b717071f1eecb2972df
compiler:       Debian clang version 20.1.8 (++20250708063551+0c9f909b7976-1~exp1~20250708183702.136), Debian LLD 20.1.8
patch:          https://syzkaller.appspot.com/x/patch.diff?x=15617542580000


       reply	other threads:[~2025-10-17 19:46 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20251017192527.214711-1-hsukrut3@gmail.com>
2025-10-17 19:46 ` syzbot [this message]
     [not found] <177644282959.3787227.1651052329897208294@talencesecurity.com>
2026-04-17 17:36 ` [syzbot] [jfs?] UBSAN: shift-out-of-bounds in dbAllocAG (3) syzbot
     [not found] <20260417101203.2489628-1-tristmd@gmail.com>
2026-04-17 10:33 ` syzbot
     [not found] <20251017201304.218523-1-hsukrut3@gmail.com>
2025-10-17 21:05 ` syzbot
2025-10-17  8:13 [PATCH] jfs: test syz test Pei Xiao
2025-10-17 10:52 ` [syzbot] [jfs?] UBSAN: shift-out-of-bounds in dbAllocAG (3) syzbot
  -- strict thread matches above, loose matches on Subject: below --
2025-10-17  4:35 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=68f29cfb.050a0220.1186a4.0519.GAE@google.com \
    --to=syzbot+4b717071f1eecb2972df@syzkaller.appspotmail.com \
    --cc=hsukrut3@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.