From: michi1@michaelblizek.twilightparadox.com (Michael Blizek)
To: kernelnewbies@lists.kernelnewbies.org
Subject: Avoid mandatory locks? Really? According to linux/Documentation/filesystems/mandatory-locking.txt
Date: Wed, 30 Mar 2011 07:54:51 +0200 [thread overview]
Message-ID: <20110330055451.GA2043@michaelblizek.twilightparadox.com> (raw)
In-Reply-To: <AANLkTiktrJ6oxPRhio8BscCDb3eNrkax0oLhUfOHFh7x@mail.gmail.com>
Hi!
On 19:14 Tue 29 Mar , Kevin O'Gorman wrote:
...
> Naturally, wanting to get the details right, I did some browsing of
> documentation. It seems the Stevens &
> Rago text that I'm using has a pretty good section on file locking in the
> Advanced I/O chapter, and it agreed
> with what I had expected well enough. But I found a reference to this file
> mentioned above, and was
> shocked to find it began with a warning to avoid this feature. It seemed it
> was like the BUGS section of
> the linux man page for the gets() function: do not use gets. I gave up on
> this topic, but told my students
> about it.
You might find these pages interesting:
http://0pointer.de/blog/projects/locking.html
http://0pointer.de/blog/projects/locking2.html
-Michi
--
programing a layer 3+4 network protocol for mesh networks
see http://michaelblizek.twilightparadox.com
next prev parent reply other threads:[~2011-03-30 5:54 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-30 2:14 Avoid mandatory locks? Really? According to linux/Documentation/filesystems/mandatory-locking.txt Kevin O'Gorman
2011-03-30 5:54 ` Michael Blizek [this message]
2011-03-30 14:47 ` Mulyadi Santosa
[not found] ` <AANLkTik4PXTe_vaXYoWqX4pFHJJDrRuPfr+M1ONr7xuE@mail.gmail.com>
2011-03-30 15:11 ` Mulyadi Santosa
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=20110330055451.GA2043@michaelblizek.twilightparadox.com \
--to=michi1@michaelblizek.twilightparadox.com \
--cc=kernelnewbies@lists.kernelnewbies.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;
as well as URLs for NNTP newsgroup(s).