From: Kees Cook <keescook@chromium.org>
To: syzbot <syzbot+510dcbdc6befa1e6b2f6@syzkaller.appspotmail.com>
Cc: chandan.babu@oracle.com, david@fromorbit.com, djwong@kernel.org,
ebiggers@kernel.org, hch@lst.de, linux-fsdevel@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-xfs@vger.kernel.org,
mukattreyee@gmail.com, syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [xfs?] UBSAN: array-index-out-of-bounds in xfs_attr3_leaf_add_work
Date: Sat, 30 Sep 2023 13:35:32 -0700 [thread overview]
Message-ID: <202309301334.FA4D7752@keescook> (raw)
In-Reply-To: <0000000000003c16100606974653@google.com>
On Sat, Sep 30, 2023 at 10:57:28AM -0700, syzbot wrote:
> syzbot suspects this issue was fixed by commit:
>
> commit a49bbce58ea90b14d4cb1d00681023a8606955f2
> Author: Darrick J. Wong <djwong@kernel.org>
> Date: Mon Jul 10 16:12:20 2023 +0000
>
> xfs: convert flex-array declarations in xfs attr leaf blocks
>
> bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=12eef28a680000
> start commit: f8566aa4f176 Merge tag 'x86-urgent-2023-07-01' of git://gi..
> git tree: upstream
> kernel config: https://syzkaller.appspot.com/x/.config?x=3f27fb02fc20d955
> dashboard link: https://syzkaller.appspot.com/bug?extid=510dcbdc6befa1e6b2f6
> syz repro: https://syzkaller.appspot.com/x/repro.syz?x=1652938f280000
> C reproducer: https://syzkaller.appspot.com/x/repro.c?x=14c10c40a80000
>
> If the result looks correct, please mark the issue as fixed by replying with:
Yup, that tracks. :)
#syz fix: xfs: convert flex-array declarations in xfs attr leaf blocks
-Kees
>
> For information about bisection process see: https://goo.gl/tpsmEJ#bisection
--
Kees Cook
prev parent reply other threads:[~2023-09-30 20:35 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-17 11:22 [syzbot] [xfs?] UBSAN: array-index-out-of-bounds in xfs_attr3_leaf_add_work syzbot
2023-06-19 2:02 ` Dave Chinner
2023-06-21 8:05 ` Eric Biggers
2023-06-22 9:51 ` Dave Chinner
2023-06-23 1:35 ` Eric Biggers
2023-09-30 17:57 ` syzbot
2023-09-30 20:35 ` Kees Cook [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=202309301334.FA4D7752@keescook \
--to=keescook@chromium.org \
--cc=chandan.babu@oracle.com \
--cc=david@fromorbit.com \
--cc=djwong@kernel.org \
--cc=ebiggers@kernel.org \
--cc=hch@lst.de \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-xfs@vger.kernel.org \
--cc=mukattreyee@gmail.com \
--cc=syzbot+510dcbdc6befa1e6b2f6@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.