From: Josh Aas <josha@sgi.com>
To: linux-kernel@vger.kernel.org
Subject: why hold bkl during do_coredump?
Date: Tue, 03 Aug 2004 13:52:52 -0500 [thread overview]
Message-ID: <410FDF04.9000609@sgi.com> (raw)
I'm looking at not holding the bkl during do_coredump, but I can't
figure out why its being held in the first place. I can only think of
the need to not mess with the current memory map, but mmap_sem is
currently held as well. Anybody know what is going on here?
--
Josh Aas
Silicon Graphics, Inc. (SGI)
Linux System Software
651-683-3068
next reply other threads:[~2004-08-03 18:50 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-03 18:52 Josh Aas [this message]
2004-08-05 4:18 ` why hold bkl during do_coredump? Andrew Morton
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=410FDF04.9000609@sgi.com \
--to=josha@sgi.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