[lkml]   [2007]   [Oct]   [15]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: nfs mmap adventure (was: 2.6.23-mm1)
Peter Zijlstra <> wrote:

> I get funny SIGBUS' like so:
> fault
> if (->page_mkwrite() < 0)
> nfs_vm_page_mkwrite()
> nfs_write_begin()
> nfs_flush_incompatible()
> nfs_wb_page()
> nfs_wb_page_priority()
> nfs_sync_mapping_wait()
> nfs_wait_on_request_locked()
> nfs_wait_on_request()
> nfs_wait_bit_interruptible()
> trying to figure out what to do about this...

Hmmm... It sounds like the fault handler should deliver the appropriate
signal, should ->page_mkwrite() return ERESTARTSYS, and then retry the access
instruction that caused the fault when the signal handler has finished


To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

 \ /
  Last update: 2007-10-15 16:09    [W:0.504 / U:3.312 seconds]
©2003-2018 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site