From: Steve French <smfltc@us.ibm.com>
To: Oliver Neukum <oliver@neukum.org>
Cc: Chris Friesen <cfriesen@nortelnetworks.com>,
linux-kernel@vger.kernel.org
Subject: Re: upcalls from kernel code to user space daemons
Date: 14 Jun 2004 17:54:39 -0500 [thread overview]
Message-ID: <1087253679.10367.41.camel@stevef95.austin.ibm.com> (raw)
In-Reply-To: <200406142341.13340.oliver@neukum.org>
On Mon, 2004-06-14 at 16:40, Oliver Neukum wrote:
> > > 1) getHostByName: when the kernel cifs code detects a server crashes
> > > and fails reconnecting the socket and the kernel code wants to see if
> > > the hostname now has a new ip address.
>
> Is that possible at all? It looks like that might deadlock in the page
> out code path.
>
Yes - since an upcall (indirectly) to a different process while in write
could cause writepage to write out memory to a mount - which could hang
if on an already dead tcp session, this (reconnection - failover to new
ip address if the server ip address changes after failure) may be too
risky to do in the context of writepage, but there may be a way to keep
refusing to do writepage while in the midst of this harder form of mount
reconnection - which isn't likely to be any worse than not
reconnecting. Fortunately, most tcp reconnection cases are much
simpler.
next prev parent reply other threads:[~2004-06-14 22:56 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-14 18:07 Steve French
2004-06-14 18:30 ` Chris Friesen
2004-06-14 21:40 ` Oliver Neukum
2004-06-14 21:57 ` Chris Friesen
2004-06-14 22:08 ` Bernd Petrovitsch
2004-06-14 22:22 ` Chris Friesen
2004-06-14 22:54 ` Tim Hockin
2004-06-14 23:10 ` Randy.Dunlap
2004-06-14 22:54 ` Steve French [this message]
2004-06-15 9:06 ` Oliver Neukum
2004-06-18 23:08 ` H. Peter Anvin
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=1087253679.10367.41.camel@stevef95.austin.ibm.com \
--to=smfltc@us.ibm.com \
--cc=cfriesen@nortelnetworks.com \
--cc=linux-kernel@vger.kernel.org \
--cc=oliver@neukum.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
all inboxes | Powered by JetHome®