From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: thockin@sun.com (Tim Hockin)
Cc: linux-kernel@vger.kernel.org (Linux Kernel Mailing List)
Subject: Re: /dev/nvram driver
Date: Fri, 22 Jun 2001 23:07:10 +0100 (BST) [thread overview]
Message-ID: <E15DZ54-0004FC-00@the-village.bc.nu> (raw)
In-Reply-To: <3B339380.C0D973CB@sun.com> from "Tim Hockin" at Jun 22, 2001 11:50:40 AM
> Currently it tracks O_EXCL on open() and sets a flag, whereby no other
> open() calls can succeed. Is this functionality really needed? Perhaps it
> should just be a reader/writer model : n readers or 1 writer. In that
> case, should open() block on a writer, or return -EBUSY?
Several tools expect that mode of behaviour so that they can atomically
recompute the checksum when writing low bytes of the CMOS
prev parent reply other threads:[~2001-06-22 22:08 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-06-22 18:50 Tim Hockin
2001-06-22 19:02 ` Jeff Garzik
2001-06-22 22:07 ` Alan Cox [this message]
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=E15DZ54-0004FC-00@the-village.bc.nu \
--to=alan@lxorguk.ukuu.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=thockin@sun.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
all inboxes | Powered by JetHome®