From: David Howells <dhowells@redhat.com>
To: "Liam R. Howlett" <Liam.Howlett@oracle.com>
Cc: dhowells@redhat.com, maple-tree@lists.infradead.org, linux-mm@kvack.org
Subject: Re: kernel BUG at lib/maple_tree.c:1237!
Date: Thu, 21 Mar 2024 15:09:12 +0000 [thread overview]
Message-ID: <1415330.1711033752@warthog.procyon.org.uk> (raw)
In-Reply-To: <932184.1710871728@warthog.procyon.org.uk>
Okay, it seems this was due to a double free in error handling in my modified
version of cifs. The reason it's happening in the maple tree code is that the
netfs_io_subrequest struct might match the size of the maple tree nodes and be
sharing a slab.
David
prev parent reply other threads:[~2024-03-21 15:09 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-19 18:08 kernel BUG at lib/maple_tree.c:1237! David Howells
2024-03-19 19:56 ` Liam R. Howlett
2024-03-19 19:59 ` And here's a GPF for you David Howells
2024-03-21 15:09 ` David Howells [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=1415330.1711033752@warthog.procyon.org.uk \
--to=dhowells@redhat.com \
--cc=Liam.Howlett@oracle.com \
--cc=linux-mm@kvack.org \
--cc=maple-tree@lists.infradead.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 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.