From: seth vidal <skvidal@phy.duke.edu>
To: nfs@lists.sourceforge.net
Subject: Thread in red hat bugzilla about locking
Date: 13 Apr 2002 01:22:07 -0400 [thread overview]
Message-ID: <1018675328.1594.79.camel@milo> (raw)
[-- Attachment #1: Type: text/plain, Size: 338 bytes --]
Hey,
has anyone here seen this bug:
https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=59245
and seen if the stock kernels/nfs-utils suffer from this problem?
I was going to test it but I figured I'd ask to see if its been solved
elsewhere already.
-sv
--
GPG Public Key: http://www.phy.duke.edu/~skvidal/skvidal.gpg
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 232 bytes --]
next reply other threads:[~2002-04-13 5:27 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-13 5:22 seth vidal [this message]
2002-04-13 18:50 ` Thread in red hat bugzilla about locking Trond Myklebust
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=1018675328.1594.79.camel@milo \
--to=skvidal@phy.duke.edu \
--cc=nfs@lists.sourceforge.net \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.