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

[Michael Fedrowitz]

 Hi,

forwarding an old bug report from the Debian BTS, which got forgotten
somehow...

-Michael


----- Forwarded message from Nick Bane <address@hidden> -----

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.

I resolved the problems once I made sure that /tmp was not mounted.

In case (1), /tmp happened to be mounted using smbfs into a Wintel system.
In case (2), either the nfs mount (LinuxPC:/usr) was itself mounted as /tmp
in case (a) or (b) the chrooted nfs share had its local /tmp also mounted as
in (a).

I now no longer use /tmp as a mount point.

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

Nick Bane
----- End forwarded message -----