lkml.org 
[lkml]   [2003]   [Aug]   [26]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: [PATCH] backport iget_locked from 2.5/2.6
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
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/

\
 
 \ /
  Last update: 2005-03-22 13:48    [W:0.041 / U:0.196 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site