From: Jamie Lokier <jamie@shareable.org>
To: Trond Myklebust <trond.myklebust@fys.uio.no>
Cc: David Woodhouse <dwmw2@infradead.org>,
Steve French <smfltc@us.ibm.com>,
linux-fsdevel@vger.kernel.org
Subject: Re: filesystem signal handling
Date: Wed, 28 Apr 2004 20:47:14 +0100 [thread overview]
Message-ID: <20040428194714.GA2982@mail.shareable.org> (raw)
In-Reply-To: <1083181437.2856.109.camel@lade.trondhjem.org>
Trond Myklebust wrote:
> I must admit that I'm unclear as to the full reason why we do that, but
> I guess that at least part of the problem is that we're not going to be
> reentrant if the handler decides to ignore the signal.
Eh? When a signal is handled, that is done by aborting the current
kernel operation (e.g. read), returning to userspace, letting
userspace handle the signal, and then possibly restarting the aborted
operation by doing the system call again.
How does re-entrancy come into it?
-- Jamie
next prev parent reply other threads:[~2004-04-28 19:47 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-27 16:20 filesystem behavior when low on memory and PF_MEMALLOC Steve French
2004-04-27 19:09 ` Bryan Henderson
2004-04-27 20:29 ` filesystem signal handling Steve French
2004-04-28 15:14 ` David Woodhouse
2004-04-28 17:05 ` Trond Myklebust
2004-04-28 17:14 ` David Woodhouse
2004-04-28 17:32 ` Trond Myklebust
2004-04-28 19:28 ` Jamie Lokier
2004-04-28 19:43 ` Trond Myklebust
2004-04-28 19:47 ` Jamie Lokier [this message]
2004-04-28 20:31 ` Trond Myklebust
2004-04-29 2:18 ` David Woodhouse
2004-04-29 2:53 ` Trond Myklebust
2004-04-29 6:41 ` David Woodhouse
2004-04-29 17:41 ` Bryan Henderson
2004-04-28 21:46 ` Bryan Henderson
2004-04-29 2:34 ` David Woodhouse
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=20040428194714.GA2982@mail.shareable.org \
--to=jamie@shareable.org \
--cc=dwmw2@infradead.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=smfltc@us.ibm.com \
--cc=trond.myklebust@fys.uio.no \
/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;
as well as URLs for NNTP newsgroup(s).