similar to: [klibc:master] nfsmount: Fix alignment of packet structures

In nfsmount, the function mount_call() is used to invoke both the mount and umount PRC's. These take identical arguments, but umount returns void rather than a file handle, so result should not be checked. This avoids a spurious 'incomplete reply' message if mount(2) system call fails. Signed-off-by: Erik van Konijnenburg <ekonijn@xs4all.nl> Index:

2ad780978b7c0c3e7877949f098cbd06e7c73839 broke klibc build MNTPROC_MNT and MNTPROC_UMNT no longer defined. usr/kinit/nfsmount/mount.c: In function ?mount_call?: usr/kinit/nfsmount/mount.c:179: error: ?MNTPROC_MNT? undeclared (first use in this function) usr/kinit/nfsmount/mount.c:179: error: (Each undeclared identifier is reported only once usr/kinit/nfsmount/mount.c:179: error: for each function

hello hpa, current chroot util stands out as broken and found an old nfsmount commit on a stray testbox in our institue. thanks for taking a look! maks git pull git://git.debian.org/~maks/klibc.git maks for the changes: maximilian attems (4): [klibc] malloc fix compile with DEBUG_MALLOC [klibc] README: add klibc email [klibc] nfsmount: improve error message [klibc]

Without this patch gcc 4.6 warns: KLIBCCC usr/kinit/nfsmount/dummypmap.o usr/kinit/nfsmount/dummypmap.c: In function 'dummy_portmap': usr/kinit/nfsmount/dummypmap.c:191:13: warning: array subscript is below array bounds [-Warray-bounds] Signed-off-by: Greg Thelen <gthelen at google.com> --- usr/kinit/nfsmount/dummypmap.c | 2 +- 1 files changed, 1 insertions(+), 1 deletions(-)

Hi all, I have implemented portmap spoofing in klibc nfsmount (released as klibc-0.144) This is basically a vestigial portmap daemon which gets launched before the mount() call and then just records any transactions it gets to a file and sends back an affirmative reply. There are two ways to use it (this belongs in a README file, but it's too late at night right now): a) Set a fixed

use AF_INET directly. Signed-off-by: maximilian attems <max at stro.at> --- usr/kinit/nfsmount/dummypmap.c | 2 +- usr/kinit/nfsmount/mount.c | 4 ++-- usr/kinit/nfsmount/sunrpc.c | 4 ++-- 3 files changed, 5 insertions(+), 5 deletions(-) diff --git a/usr/kinit/nfsmount/dummypmap.c b/usr/kinit/nfsmount/dummypmap.c index 43abe37..481e23b 100644 ---

Hi everybody and thanks to those persons who make klibc being possible. I am booting a lessdisks system from a server. I have got it in NFSv3 but I would like use the features of NFSv4. I am using initramfs-tools so I have in my initrd.img the utility nfsmount wich make possible booting in NFSv3. I would like know if exists some version of nfsmount or some patch or, if does not, some program (a

The dump_fh() function in nfsmount can be misleading: always mentions NFS_FHSIZE as size, but can print more, can print nothing if passed less than 8 bytes. This is a more robust implementation also suitable for printing datastructures other than the file handle, with ASCII rendering as bonus; output like so: stuff: 0xbfffe41c, length 30 0000: 53 75 6e 20 4a 75 6e 20 20 35 20 31 34 3a 31 32

I'm booting with nfs options, but klibc doesnt like the rsize= option. This patch fixes it. console=ttyS0,38400 rw ip=eth0 root=/dev/nfs nfsroot=192.168.1.2:/nfsroot/mac,rsize=8192,wsize=8192,tcp kinit=/bin/kinit --- usr/klibc/klibc-0.81.orig/nfsmount/main.c 2003-05-06 00:15:09.000000000 +0200 +++ usr/klibc/klibc-0.81/nfsmount/main.c 2003-11-22 19:14:18.000000000 +0100 @@ -80,7

Hey all, bug report time. I started tracking this down, but am at a bit of a loss for time, so I figured I'd report over this list to see if anyone else has the time to fix this or at least find the error. When calling nfsmount on it's own, say "nfsmount 1.2.3.4:/home/nfs /root" it works just fine, however, when calling nfsmount_main from within kinit (via nfsroot=), things get

Hi everybody I'm booting a diskless workstation using nfsmount (included in the initial ramdisk). First time I try to boot the diskless node, it says this error: "nfs: server 192.168.1.33 not responding, timed out nfs: server 192.168.1.33 not responding, timed out mount: I/O error short read: 0 < 28" althought in the /var/log/syslog file of the server appears the message:

Hi, In a discussion on the kernel bugzilla (bug 11154) the question of NFS mount options came up. Trond Myklebust seems to consider the default nfsmount options (V3 over TCP, with timeo=7 and retrans=3) to be bad. I don't know yet if that's my problem, but anyway, would you consider changing the defaults to timeo=600 and retrans=2, if only just to match the default util-linux mount

linux-2.6 2ad780978b7c0c3e7877949f098cbd06e7c73839 cleaned up linux/nfsmount.h and thus a klibc build would produce this: > usr/kinit/nfsmount/mount.c:179: error: 'MNTPROC_MNT' undeclared (first use in this function) > usr/kinit/nfsmount/mount.c:179: error: (Each undeclared identifier is reported only once > usr/kinit/nfsmount/mount.c:179: error: for each function it appears

Missing unwrap on error path.. Signed-off-by: maximilian attems <max at stro.at> --- usr/kinit/nfsmount/main.c | 6 +++++- 1 files changed, 5 insertions(+), 1 deletions(-) diff --git a/usr/kinit/nfsmount/main.c b/usr/kinit/nfsmount/main.c index beda723..b85901a 100644 --- a/usr/kinit/nfsmount/main.c +++ b/usr/kinit/nfsmount/main.c @@ -214,6 +214,7 @@ int nfsmount_main(int argc, char

gcc picked up a couple of suspicious memset lengths which turned out to be real bugs. Signed-off-by: Anton Blanchard <anton at samba.org> --- usr/kinit/nfsmount/sunrpc.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/usr/kinit/nfsmount/sunrpc.c b/usr/kinit/nfsmount/sunrpc.c index 0628cef..0a7fcf5 100644 --- a/usr/kinit/nfsmount/sunrpc.c +++

Commit-ID: 71a849a7e2d5e73321e986fa91d1f34b387e71ba Gitweb: http://git.kernel.org/?p=libs/klibc/klibc.git;a=commit;h=71a849a7e2d5e73321e986fa91d1f34b387e71ba Author: Anton Blanchard <anton at samba.org> AuthorDate: Tue, 3 Dec 2013 18:14:58 +1100 Committer: H. Peter Anvin <hpa at zytor.com> CommitDate: Tue, 3 Dec 2013 10:53:38 -0800 [klibc] nfsmount: memset uses sizeof

The standard mount option nowadays to specify NFS version is "nfsvers", as documented in nfs(5) on modern Linux systems. Up to now, nfsmount only supported the old "v2" or "v3" boolean options. Extend option parsing to support both "nfsvers=X" and "vers=X", with X being equal to either 2 or 3 (nfsmount does not support NFSv4 at present). If both

Commit-ID: c4b811a1e4647224ddc717fac59900d16d0e9d4d Gitweb: http://git.kernel.org/?p=libs/klibc/klibc.git;a=commit;h=c4b811a1e4647224ddc717fac59900d16d0e9d4d Author: Baptiste Jonglez <baptiste.jonglez at imag.fr> AuthorDate: Thu, 14 Sep 2017 09:22:21 -0700 Committer: Ben Hutchings <ben at decadent.org.uk> CommitDate: Wed, 2 Jan 2019 03:08:04 +0000 [klibc] nfsmount: support

I managed to get to the bottom of this, and filed a bug report for NFS: https://bugzilla.kernel.org/show_bug.cgi?id=204939 Klibc nfsmount still a bug: it needs to NOT hardcode timeo=7. Either the NFS defaults should be used, which result in: timeo=600,rsize=1048576,wsize=1048576, or at least the kernel documented defaults, https://www.kernel.org/doc/Documentation/filesystems/nfs/nfsroot.txt

Commit-ID: 886783e7a10fb7a638bc6034e4cdcb6296cea6a1 Gitweb: http://git.kernel.org/?p=libs/klibc/klibc.git;a=commit;h=886783e7a10fb7a638bc6034e4cdcb6296cea6a1 Author: Ben Hutchings <ben at decadent.org.uk> AuthorDate: Mon, 7 Oct 2019 17:18:41 +0100 Committer: Ben Hutchings <ben at decadent.org.uk> CommitDate: Mon, 7 Oct 2019 17:27:49 +0100 [klibc] nfsmount: Use kernel