Re: [fuse-devel] SIGBUS to toplevel process

[Roberto G. <bob...@gm...>]

On Fri, 2010-01-29 at 15:57 -0800, Rudd-O wrote:
> SIGBUS is when some file mmapped() by the process changed from
> underneath and that caused the program to issue a wrong memory access to
> the mapped file.
> 
For the records: I've find solution.

Problem was in my rename() handler, called by FUSE on unlink() to move
the removed but yet opened file. I implemented that to create a
different file and move only contents (which is not a normal path, but I
need that), but this behaviour would invalidate the file descriptor and
produced an invalid access.

Correcting that behaviour on some particular corner case (so: performing
a regular rename() when I don't really need a brand new file) permits
correct execution.

-- 
Roberto -MadBob- Guido
http://claimid.com/madbob