From: Pekka Enberg <penberg@cs.helsinki.fi>
To: schwidefsky@de.ibm.com
Cc: Michael Holzheu <HOLZHEU@de.ibm.com>,
linux-kernel@vger.kernel.org, mschwid2@de.ibm.com,
linux-fsdevel@vger.kernel.org
Subject: Re: [PATCH/RFC] s390: Hypervisor File System
Date: Tue, 25 Apr 2006 17:04:14 +0300 [thread overview]
Message-ID: <1145973854.11508.7.camel@localhost> (raw)
In-Reply-To: <1145637630.6884.7.camel@localhost>
Hi Martin,
On Fri, 2006-04-21 at 18:38 +0300, Pekka Enberg wrote:
> > The update-on-write to special file thing seems bit strange to me. What
> > if two processes ask for it at the same time?
On Fri, 2006-04-21 at 18:40 +0200, Martin Schwidefsky wrote:
> Yes, we had that discussion as well. Any sensible suggestion how to do
> it in a more clever way would be greatly appreciated. We haven't found
> something better so far.
The only way I can think of is via s_ops->remount_fs. That's bit safer
anyway, as sb->s_lock protects us from concurrent updates. I am cc'ing
fsdevel to see if they can come up with a better suggestion.
Pekka
parent reply other threads:[~2006-04-25 14:04 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <1145637630.6884.7.camel@localhost>]
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=1145973854.11508.7.camel@localhost \
--to=penberg@cs.helsinki.fi \
--cc=HOLZHEU@de.ibm.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mschwid2@de.ibm.com \
--cc=schwidefsky@de.ibm.com \
/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).