From: Matthew Wilcox <willy@infradead.org>
To: Dave Kleikamp <dave.kleikamp@oracle.com>
Cc: Manas Ghandat <ghandatmanas@gmail.com>,
Linux-kernel-mentees@lists.linuxfoundation.org,
jfs-discussion@lists.sourceforge.net,
linux-kernel@vger.kernel.org,
syzbot+411debe54d318eaed386@syzkaller.appspotmail.com,
Sasha Levin <sashal@kernel.org>
Subject: Re: [PATCH] jfs: fix shift-out-of-bounds in dbJoin
Date: Mon, 29 Jan 2024 14:55:47 +0000 [thread overview]
Message-ID: <Zbe8c_CPNP8IdphB@casper.infradead.org> (raw)
In-Reply-To: <a25c75af-c961-4ca6-9810-dbcfe64753d5@oracle.com>
On Mon, Jan 29, 2024 at 08:39:18AM -0600, Dave Kleikamp wrote:
> On 1/28/24 2:49PM, Matthew Wilcox wrote:
> > On Wed, Oct 11, 2023 at 08:09:37PM +0530, Manas Ghandat wrote:
> > > Currently while joining the leaf in a buddy system there is shift out
> > > of bound error in calculation of BUDSIZE. Added the required check
> > > to the BUDSIZE and fixed the documentation as well.
> >
> > This patch causes xfstests to fail frequently. The one this trace is
> > from was generic/074.
>
> Thanks for catching this. The sanity test is not right, so we need to revert
> that one.
Unfortunately, my overnight test run with this patch reverted crashed
again with the same signature. I also reverted the parent commit,
and when that crashed I also reverted the parent of that. Which also
crashed.
So maybe there's something else that makes this unstable. Or maybe my
bisect went wrong. Or _something_. Anyway, I'm going to spend much of
today hammering on generic/074 with various kernel versions and see what
I can deduce.
So far I see no evidence that v6.7 crashes with g/074. And I know that
next-20240125 does crash with g/074. I'm pretty sure that v6.8-rc1 also
crashes with g/074, but will confirm that.
next prev parent reply other threads:[~2024-01-29 14:55 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-11 14:39 [PATCH] jfs: fix shift-out-of-bounds in dbJoin Manas Ghandat
2023-10-11 14:39 ` Manas Ghandat
2023-10-16 15:00 ` Manas Ghandat
2023-10-16 15:00 ` Manas Ghandat
2023-11-01 6:42 ` Manas Ghandat
2023-11-01 6:42 ` Manas Ghandat
2023-11-01 15:57 ` Dave Kleikamp
2023-11-01 15:57 ` Dave Kleikamp
2024-01-28 20:49 ` Matthew Wilcox
2024-01-29 14:39 ` Dave Kleikamp
2024-01-29 14:55 ` Matthew Wilcox [this message]
2024-01-29 15:00 ` Dave Kleikamp
2024-01-29 18:29 ` Matthew Wilcox
2024-01-29 21:17 ` Dave Kleikamp
2024-01-29 22:13 ` Matthew Wilcox
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=Zbe8c_CPNP8IdphB@casper.infradead.org \
--to=willy@infradead.org \
--cc=Linux-kernel-mentees@lists.linuxfoundation.org \
--cc=dave.kleikamp@oracle.com \
--cc=ghandatmanas@gmail.com \
--cc=jfs-discussion@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=sashal@kernel.org \
--cc=syzbot+411debe54d318eaed386@syzkaller.appspotmail.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.