Re: 2.4.0-test10-pre3:Oops in mm/filemap.c:filemap_write_pa

[Alexander Viro]

On 20 Oct 2000, Trond Myklebust wrote:

> >>>>> " " == Russell King <[EMAIL PROTECTED]> writes:
> 
>      > invalidate_inode_pages nfs_zap_caches nfs_lock fcntl_setlk
>      > do_fcntl sys_fcntl
> 
>      > So I guess that NFS locking is really bad if the region is
>      > mmapped!
> 
> Yep, but that's a symptom, not a cause. We want to be able to run
> invalidate_inode_pages() safely at any moment, since the need can be
> triggered externally (because the server and client page caches
> disagree).

So what exactly do you want it to do when page is mapped by user process?
Should it remain visible or not? What should happen if process writes to
that page?

Trond, I'm not asking about implementation - the question being what
semantics do you want for nfs_zap_caches() wrt user-mapped pages.


-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
Please read the FAQ at http://www.tux.org/lkml/