lkml.org 
[lkml]   [1999]   [Nov]   [25]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: inode_lock "decorative"?


On Thu, 25 Nov 1999, Andrea Arcangeli wrote:

> What I ask you is _why_ you increment and the iput by hand. Just remove
> the i_count++ and the iput() and all should remains fine. Basically you
> run always with an i_count of 2 while you could run all the time with an
> i_count of 1 without differences (unless I am missing something... hmm).

Correct fix is to get rid of this sock->inode thing completely. Check what
fields of ->inode are used - you'll see that we can easily get rid of that
mess. Will make things much cleaner. I can roll such patch tomorrow (after
the new cache/symlink stuff will be done).


-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/

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