Messages in this thread | | | Date | Wed, 30 May 2001 10:10:31 +0200 | Subject | Re: OOPS with 2.4.5 [kernel BUG at inode.c:486] | From | Trond Myklebust <> |
| |
>>>>> " " == Alexander Viro <viro@math.psu.edu> writes:
> On 30 May 2001, Trond Myklebust wrote:
>> Al: Is there any reason why the cases >> >> if (!inode->i_nlink) >> >> and the 'magic nfs path' should be treated differently? >> Personally, I'd rather prefer to merge the 2.
> I don't think that it's a good idea. Why not fry the cache > explicitly when you invalidate the inode?
Won't there be a race there? Imagine if some other process is busy writing to that inode, and happens to add a new page after we've truncated...
Cheers, Trond - 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/
| |