From: Bastian Blank <bastian.blank@credativ.de>
To: Jeff Layton <jlayton@kernel.org>
Cc: Ilya Dryomov <idryomov@gmail.com>,
ceph-devel@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: PROBLEM: SLAB use-after-free with ceph(fs)
Date: Tue, 4 Jan 2022 13:20:42 +0100 [thread overview]
Message-ID: <YdQ7msXTCF5kKl4V@softhammer.credativ.lan> (raw)
In-Reply-To: <22cf685dbf61e09a4e5e7c3a48d1117a769548a8.camel@kernel.org>
Hi
On Tue, Jan 04, 2022 at 07:00:31AM -0500, Jeff Layton wrote:
> On Tue, 2022-01-04 at 10:49 +0100, Bastian Blank wrote:
> > > [152791.777458] cache_from_obj: Wrong slab cache. jbd2_journal_handle but object is from kmalloc-256
> At first blush, this looks like the same problem as:
> https://tracker.ceph.com/issues/52283
> ...but that should have been fixed in v5.14.
Nope, does not make sense. This reported issue tried to free a
"ceph_cap_flush", while mine tries to free "jbd2_journal_handle", which
is far away.
> You may also want to try v5.16-rc8 if you're able to build your own
> kernels. There were some patches that went in to improve how the client
> handles inodes that become inaccessible.
I try to get them to install a 5.16-rc8 or newer, get a new crash dump
and report that to https://tracker.ceph.com/.
Thanks,
Bastian
--
Bastian Blank
Berater
Telefon: +49 2166 9901-194
E-Mail: bastian.blank@credativ.de
credativ GmbH, HRB Mönchengladbach 12080, USt-ID-Nummer: DE204566209
Trompeterallee 108, 41189 Mönchengladbach
Geschäftsführung: Dr. Michael Meskes, Geoff Richardson, Peter Lilley
Unser Umgang mit personenbezogenen Daten unterliegt
folgenden Bestimmungen: https://www.credativ.de/datenschutz
next prev parent reply other threads:[~2022-01-04 12:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-04 9:49 PROBLEM: SLAB use-after-free with ceph(fs) Bastian Blank
2022-01-04 12:00 ` Jeff Layton
2022-01-04 12:20 ` Bastian Blank [this message]
2022-01-04 12:29 ` Jeff Layton
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=YdQ7msXTCF5kKl4V@softhammer.credativ.lan \
--to=bastian.blank@credativ.de \
--cc=ceph-devel@vger.kernel.org \
--cc=idryomov@gmail.com \
--cc=jlayton@kernel.org \
--cc=linux-kernel@vger.kernel.org \
/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