From: Chris Mason <mason@suse.com>
To: Oleg Drokin <green@namesys.com>
Cc: linux-kernel@vger.kernel.org, eazgwmir@umail.furryterror.org,
viro@math.psu.edu, nikita@namesys.com
Subject: Re: [2.4] VFS locking problem during concurrent link/unlink
Date: 16 Jan 2003 10:39:41 -0500 [thread overview]
Message-ID: <1042731580.31099.2195.camel@tiny.suse.com> (raw)
In-Reply-To: <20030116140015.A17612@namesys.com>
On Thu, 2003-01-16 at 06:00, Oleg Drokin wrote:
> Hello!
>
> Debugging reiserfs problem that can be demonstrated with script created by
> Zygo Blaxell, I started to wonder if the problem presented is indeed reiserfs
> fault and not VFS.
> Though the Zygo claims script only produces problems on reiserfs, I am trying
> it now myself on ext2 (which will take some time).
>
> Debugging shows that reiserfs_link is sometimes called for inodes whose
> i_nlink is zero (and all corresponding data is deleted already).
> So my current guess of what's going on is this:
>
No, this is a reiserfs bug, since we schedule after doing link checks in
reiserfs_link and reiserfs_unlink. I sent a patch to reiserfs dev a
while ago, I'll pull it out of the suse kernel and rediff against
2.4.20.
-chris
next prev parent reply other threads:[~2003-01-16 15:31 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-16 11:00 [2.4] VFS locking problem during concurrent link/unlink Oleg Drokin
2003-01-16 15:39 ` Chris Mason [this message]
2003-01-16 15:43 ` Oleg Drokin
2003-01-16 16:02 ` Chris Mason
2003-01-16 16:06 ` Nikita Danilov
2003-01-16 16:22 ` Chris Mason
2003-01-16 17:03 ` Oleg Drokin
2003-01-16 17:20 ` Oleg Drokin
2003-01-16 16:07 ` Oleg Drokin
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=1042731580.31099.2195.camel@tiny.suse.com \
--to=mason@suse.com \
--cc=eazgwmir@umail.furryterror.org \
--cc=green@namesys.com \
--cc=linux-kernel@vger.kernel.org \
--cc=nikita@namesys.com \
--cc=viro@math.psu.edu \
/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