From: Christoph Hellwig <hch@lst.de>
To: Venkat Rao Bagalkote <venkat88@linux.vnet.ibm.com>
Cc: linux-kernel@vger.kernel.org, linuxppc-dev@lists.ozlabs.org,
hch@lst.de, brauner@kernel.org, sfr@canb.auug.org.au
Subject: Re: [linux-next][20241004]BUG: KFENCE: memory corruption in xfs_iext_remove+0x288/0x2c8 [xfs]
Date: Thu, 10 Oct 2024 10:09:27 +0200 [thread overview]
Message-ID: <20241010080927.GA7980@lst.de> (raw)
In-Reply-To: <20241008063307.GA22312@lst.de>
On Tue, Oct 08, 2024 at 08:33:07AM +0200, Christoph Hellwig wrote:
> On Mon, Oct 07, 2024 at 07:34:18PM +0530, Venkat Rao Bagalkote wrote:
> > Greetings!!!
> >
> >
> > Observing Kfence errors, while running fsstress test on Power PC platform
>
> Is this new or is this the first time you run kfence? Any chance you
> could bisect it?
FYI, Marco Elver ever pointed out that this was an issue with kfence vs
krealloc and the offending changes have been dropped from linux-next.
prev parent reply other threads:[~2024-10-10 8:09 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-07 14:04 [linux-next][20241004]BUG: KFENCE: memory corruption in xfs_iext_remove+0x288/0x2c8 [xfs] Venkat Rao Bagalkote
2024-10-08 6:33 ` Christoph Hellwig
2024-10-10 8:09 ` Christoph Hellwig [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=20241010080927.GA7980@lst.de \
--to=hch@lst.de \
--cc=brauner@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=sfr@canb.auug.org.au \
--cc=venkat88@linux.vnet.ibm.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).