lkml.org 
[lkml]   [1998]   [Jul]   [22]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
From
SubjectRe: inodes are not cleared!
Date
Hello!

> The general inode code does only a minimal clearing of fields for
> performance reasons. Most filesystems want to set the i_flags value
> themselves, or else don't use it at all.
>
> Assuming that the inode in question was for a socket, I would suggest
> clearing i_flags in the socket code instead.

OK. Could you look, what fields are used by VFS and not cleared there?

To be honest, I suspect you are not right here.
At least, networking asked for get_empty_inode(),
so that it has right to expect really empty one 8)

Look at "struct inode", it contains whole screen of fields.
We cannot expect, that networking in general
(and particularly, me 8)) knows something about i_flock, i_mmap etc. etc.

At least, if get_empty_inode() is not supposed to return
empty inode, VFS should export a function to clear it.

Alexey

-
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.altern.org/andrebalsa/doc/lkml-faq.html

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