From: Oleg Drokin <green@namesys.com>
To: Chris Mason <mason@suse.com>
Cc: Nikita Danilov <Nikita@Namesys.COM>,
linux-kernel@vger.kernel.org, eazgwmir@umail.furryterror.org,
viro@math.psu.edu
Subject: Re: [2.4] VFS locking problem during concurrent link/unlink
Date: Thu, 16 Jan 2003 20:03:41 +0300 [thread overview]
Message-ID: <20030116200341.A1002@namesys.com> (raw)
In-Reply-To: <1042734151.31095.2211.camel@tiny.suse.com>
Hello!
On Thu, Jan 16, 2003 at 11:22:32AM -0500, Chris Mason wrote:
> They inc the link count in ext2_link before scheduling. The patch below
> is what I had in mind, but is untested.
It does not change anything.
Bye,
Oleg
next prev parent reply other threads:[~2003-01-16 16:54 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
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 [this message]
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=20030116200341.A1002@namesys.com \
--to=green@namesys.com \
--cc=Nikita@Namesys.COM \
--cc=eazgwmir@umail.furryterror.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mason@suse.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