From: Chad Talbott <chadt@sgi.com>
To: linux-kernel@vger.kernel.org
Subject: NFS core dump blocks
Date: 31 Mar 2003 16:51:23 -0800 [thread overview]
Message-ID: <6eoznnbnipg.fsf@sgi.com> (raw)
This is not an issue in 2.5, but in 2.4:
When running a large app over NFS, it crashes and dumps core. This
takes some time, during which ps, top, and other customers of /proc
hang while they wait for the mmap_sem. Is there an argument against
changing the
down_write(¤t->mm->mmap_sem);
in fs/binfmt_elf.c:elf_core_dump to
down_read(¤t->mm->mmap_sem);
Thanks,
Chad
reply other threads:[~2003-04-01 0:40 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=6eoznnbnipg.fsf@sgi.com \
--to=chadt@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