All of lore.kernel.org
 help / color / mirror / Atom feed
From: Aleksandr Nogikh <nogikh@google.com>
To: syzbot <syzbot+b9ba793adebb63e56dba@syzkaller.appspotmail.com>
Cc: dave.kleikamp@oracle.com, jfs-discussion@lists.sourceforge.net,
	linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
	liushixin2@huawei.com, shaggy@kernel.org,
	syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [jfs?] UBSAN: shift-out-of-bounds in dbAllocBits
Date: Wed, 22 Mar 2023 22:30:58 +0100	[thread overview]
Message-ID: <CANp29Y5825vdNCe1JUmasczU5AkNPKKWBzPUmjbNxKj3EapG4w@mail.gmail.com> (raw)
In-Reply-To: <0000000000007af84a05f77fa920@google.com>

On Wed, Mar 22, 2023 at 5:29 PM syzbot
<syzbot+b9ba793adebb63e56dba@syzkaller.appspotmail.com> wrote:
>
> syzbot suspects this issue was fixed by commit:
>
> commit fad376fce0af58deebc5075b8539dc05bf639af3
> Author: Liu Shixin via Jfs-discussion <jfs-discussion@lists.sourceforge.net>
> Date:   Thu Nov 3 03:01:59 2022 +0000
>
>     fs/jfs: fix shift exponent db_agl2size negative
>
> bisection log:  https://syzkaller.appspot.com/x/bisect.txt?x=12d90bf6c80000
> start commit:   a6afa4199d3d Merge tag 'mailbox-v6.1' of git://git.linaro...
> git tree:       upstream
> kernel config:  https://syzkaller.appspot.com/x/.config?x=d19f5d16783f901
> dashboard link: https://syzkaller.appspot.com/bug?extid=b9ba793adebb63e56dba
> syz repro:      https://syzkaller.appspot.com/x/repro.syz?x=1322ae34880000
> C reproducer:   https://syzkaller.appspot.com/x/repro.c?x=10403c94880000
>
> If the result looks correct, please mark the issue as fixed by replying with:
>
> #syz fix: fs/jfs: fix shift exponent db_agl2size negative
>


Looks reasonable.

#syz fix: fs/jfs: fix shift exponent db_agl2size negative

      reply	other threads:[~2023-03-22 21:31 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-10  7:16 [syzbot] UBSAN: shift-out-of-bounds in dbAllocBits syzbot
2023-03-22 16:29 ` [syzbot] [jfs?] " syzbot
2023-03-22 21:30   ` Aleksandr Nogikh [this message]

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=CANp29Y5825vdNCe1JUmasczU5AkNPKKWBzPUmjbNxKj3EapG4w@mail.gmail.com \
    --to=nogikh@google.com \
    --cc=dave.kleikamp@oracle.com \
    --cc=jfs-discussion@lists.sourceforge.net \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=liushixin2@huawei.com \
    --cc=shaggy@kernel.org \
    --cc=syzbot+b9ba793adebb63e56dba@syzkaller.appspotmail.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 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.