Re: address@hidden: Patch problems if /tmp is a network mount]

[Paul Eggert]

> From: "Nick Bane" <address@hidden>
> To: <address@hidden>
> Subject: Patch problems if /tmp is a network mount
> 
> Package: Patch
> Version: 2.5 and 2.5.4-5
> 
> 1) While patching kernels 2.4.7 and 2.4.10, I noted problems with null
> characters being appended to many (presumably the patched) files. This was
> on an x86 using patch 2.5 and 2.5.4-5
> 
> 2) I also experienced problems patching files using a Compaq H3600 networked
> into the x86 using the same files. These problems were an inability of patch
> to set the attributes due to a stale (inode/handle/something) target. This
> was true whether the directory structure was (a) simply nfs mounted or (b)
> via a chrooted and secondary mount via nfs. This was using the arm version
> of patch 2.5.

It's not clear to me that this was a problem with 'patch' per se.  It
could well be a problem with the way that the filesystems were
implemented, and if so the bug would probably affect programs other
than 'patch'.  Either way, the problem would need to be investigated
further, probably with a debugger on 'patch', to find out where the
null bytes were coming from.

> This is my first bug report. I hope it is suitably presented.

Yes, it is.  Thanks.