From: Oleg Drokin <green@namesys.com>
To: Christoph Hellwig <hch@lst.de>,
marcelo@hera.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] backport iget_locked from 2.5/2.6
Date: Tue, 26 Aug 2003 18:35:30 +0400 [thread overview]
Message-ID: <20030826143530.GD23462@namesys.com> (raw)
In-Reply-To: <20030826143024.GA4184@lst.de>
Hello!
On Tue, Aug 26, 2003 at 04:30:24PM +0200, Christoph Hellwig wrote:
> > > Mail-Followup-To: Christoph Hellwig <hch@angband.namesys.com>,
> > Hm, very interesting header, I'd say. No wonder I'm getting errors replying to
> > your emails.
> Well, I got the same from you although I though only in the Cc line
> which I removed.
That's because I hit "reply" first time and have not looked at the CC list.
> > > > The patch below does not achieve this. We still fill inode private part
> > > > outside of inode_lock locked region.
> > > -ENOPATCH :)
> > I meant the patch in the email you sent and to which I answered originally ;)
> Sorry, I missed the 'not' when reading and though you had an alternate
> patch
Actually, I have altenate patch (but no, I have not tried to attach it) ;)
I have full iget5_locked backport (that I was sending around some time ago). Only it
will break every iget4 user not in the tree (by changing VFS API), so I guess it is not an option.
But if people think it is good idea to adapt this change, I can easily resurrect that patch, of course.
Bye,
Oleg
prev parent reply other threads:[~2003-08-26 14:41 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-25 14:07 [PATCH] backport iget_locked from 2.5/2.6 Christoph Hellwig
2003-08-26 11:27 ` Oleg Drokin
2003-08-26 13:48 ` Christoph Hellwig
2003-08-26 13:54 ` Oleg Drokin
2003-08-26 14:30 ` Christoph Hellwig
2003-08-26 14:35 ` Oleg Drokin [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=20030826143530.GD23462@namesys.com \
--to=green@namesys.com \
--cc=hch@lst.de \
--cc=linux-kernel@vger.kernel.org \
--cc=marcelo@hera.kernel.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).