From: Ivan Kanis <ivank@wrq.com>
To: Trond Myklebust <trond.myklebust@fys.uio.no>
Cc: Neil Brown <neilb@cse.unsw.edu.au>,
linux-kernel@vger.kernel.org, nfs-devel@linux.kernel.org,
Paul Pietromonaco <paulp@wrq.com>
Subject: Re: [BUG] knfsd causes file system corruption when files are locked.
Date: Mon, 20 Nov 2000 10:43:04 -0800 (PST) [thread overview]
Message-ID: <14873.28856.472146.691962@jedi.wrq.com> (raw)
In-Reply-To: <shsofzg9e6y.fsf@charged.uio.no>
In-Reply-To: <14867.6967.292440.394045@jedi.wrq.com> <14867.9090.689736.462761@notabene.cse.unsw.edu.au> <14867.18905.212001.355827@jedi.wrq.com> <shsofzg9e6y.fsf@charged.uio.no>
>>>>> "Trond" == Trond Myklebust <trond.myklebust@fys.uio.no> writes:
>>>>> " " == Ivan Kanis <ivank@wrq.com> writes:
Ivan> space. I am running this on ext2fs. Fsck-ing the filesystem
Ivan> does not help. The only way to recover the space is to
Ivan> reformat the partition.
Ivan>
Ivan> [3.] knfsd, lock, NLM_SHARE, NLM_UNSHARE
Ivan>
Ivan> [4.] Linux version 2.2.16 (root@jedi) (gcc version 2.7.2.3)
Trond> Please dig around in dejanews for the locking patch I
Trond> posted on l-k last week (to be applied on top of
Trond> 2.2.18pre21). It fixes 3 leaks in the locking code (amongst
Trond> them the share leak).
Hi Trond,
Fantastic news: your patches fixed the bug! I hope it will make it in
the kernel pretty soon, I will be testing it some more today.
Thank you,
Ivan Kanis
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
prev parent reply other threads:[~2000-11-20 19:14 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-11-15 23:24 Ivan Kanis
2000-11-16 0:00 ` Neil Brown
2000-11-16 2:43 ` Ivan Kanis
2000-11-16 14:36 ` Trond Myklebust
2000-11-20 18:43 ` Ivan Kanis [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=14873.28856.472146.691962@jedi.wrq.com \
--to=ivank@wrq.com \
--cc=linux-kernel@vger.kernel.org \
--cc=neilb@cse.unsw.edu.au \
--cc=nfs-devel@linux.kernel.org \
--cc=paulp@wrq.com \
--cc=trond.myklebust@fys.uio.no \
/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®