From: David Howells <dhowells@redhat.com>
To: Aubrey <aubreylee@gmail.com>
Cc: linux-kernel@vger.kernel.org, mpm@selenic.com,
dhowells@redhat.com, davidm@snapgear.com, gerg@snapgear.com
Subject: Re: kernel BUGs when removing largish files with the SLOB allocator
Date: Mon, 04 Sep 2006 11:21:35 +0100 [thread overview]
Message-ID: <17162.1157365295@warthog.cambridge.redhat.com> (raw)
In-Reply-To: <6d6a94c50609032356t47950e40lbf77f15136e67bc5@mail.gmail.com>
Aubrey <aubreylee@gmail.com> wrote:
> Is there any solution/patch to fix the issue?
Make the SLOB allocator mark its pages PG_slab, just like the SLAB allocator
does. I think this should be okay as the SLOB allocator and the SLAB
allocator seem to be mutually exclusive.
Using PG_slab would also give an instant check to things like SLOB's kfree().
> +#ifdef CONFIG_SLAB
> if (PageSlab(page))
> +#endif
This is not a valid workaround as the object won't necessarily have been
allocated from a slab (shared ramfs mappings and SYSV SHM for example). You
may not pass to ksize() objects allocated by means other than SLAB/SLOB.
David
--
VGER BF report: H 1.12398e-05
next prev parent reply other threads:[~2006-09-04 10:21 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-04 6:56 kernel BUGs when removing largish files with the SLOB allocator Aubrey
2006-09-04 10:21 ` David Howells [this message]
2006-09-05 3:52 ` Aubrey
2006-09-05 9:35 ` David Howells
2006-09-06 2:35 ` Aubrey
2006-09-06 3:36 ` Nick Piggin
2006-09-12 8:07 ` Aubrey
2006-09-12 8:54 ` David Howells
2006-09-12 10:53 ` Aubrey
2006-09-12 17:43 ` Matt Mackall
2006-09-12 19:10 ` David Howells
2006-09-12 20:51 ` Matt Mackall
2006-09-12 20:56 ` David Howells
2006-09-12 21:04 ` Matt Mackall
2006-09-12 21:59 ` David Howells
2006-09-13 19:39 ` Matt Mackall
2006-09-13 2:16 ` Nick Piggin
2006-09-13 7:21 ` Aubrey
2006-09-12 19:25 ` David Howells
2006-09-12 20:28 ` Matt Mackall
2006-09-12 21:02 ` David Howells
2006-09-12 21:15 ` Matt Mackall
2006-09-12 20:49 ` Matt Mackall
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=17162.1157365295@warthog.cambridge.redhat.com \
--to=dhowells@redhat.com \
--cc=aubreylee@gmail.com \
--cc=davidm@snapgear.com \
--cc=gerg@snapgear.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mpm@selenic.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