From: Andi Kleen <ak@suse.de>
To: Elisheva Alexander <ealexand@checkpoint.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: buffer_head slab memory leak, Linux bug?
Date: 02 Sep 2001 15:13:27 +0200 [thread overview]
Message-ID: <oupbsktzqfc.fsf@pigdrop.muc.suse.de> (raw)
In-Reply-To: <20010902140126.E28228@checkpoint.com.suse.lists.linux.kernel>
In-Reply-To: Elisheva Alexander's message of "2 Sep 2001 13:18:17 +0200"
Elisheva Alexander <ealexand@checkpoint.com> writes:
> it happens quite often (at random), so it's not too hard to recreate it.
It is linux telling you that your code is crappy ;)
It's easy to fix. You just need to fix the lock to not turn off interrupts
for such a long time. If you're writing non driver network code you likely don't need
an _irqsave lock anyways, as a _bh lock should suffice. Better would be to use
a different lock structure however for such long locks that do not depend on blocking
bottom halves or interrupts (e.g. see how the TCP socket lock works as an example)
-Andi
next parent reply other threads:[~2001-09-02 13:13 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20010902140126.E28228@checkpoint.com.suse.lists.linux.kernel>
2001-09-02 13:13 ` Andi Kleen [this message]
2001-09-02 11:01 buffer_head slab memory leak, Linux bug? Elisheva Alexander
2001-09-02 12:46 ` Alan Cox
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=oupbsktzqfc.fsf@pigdrop.muc.suse.de \
--to=ak@suse.de \
--cc=ealexand@checkpoint.com \
--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