similar to: [klibc:master] nfsmount: memset uses sizeof pointer as length

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 +++

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 ---

Various coding style fixes checkpatch warns about. The goal is not to be 100% checkpatch compliant, but to have more consistent coding style. As this is a trivial patch serie, will land in 24 hours in klibc git, unless of course ml review hits a bugger. Checked with size(3) that the generated kinit, fstype, ipconfig and nfsmount are the same. maximilian attems (4): [klibc] ipconfig: reduce

Commit-ID: 029622dfbfe25203275a385a5bf33d44c2409b00 Gitweb: http://git.kernel.org/?p=libs/klibc/klibc.git;a=commit;h=029622dfbfe25203275a385a5bf33d44c2409b00 Author: Benjamin Cama <benjamin.cama at telecom-bretagne.eu> AuthorDate: Fri, 22 Jun 2012 12:17:01 +0200 Committer: maximilian attems <max at stro.at> CommitDate: Thu, 28 Jun 2012 17:23:14 +0200 [klibc] nfsmount: Fix

nfsmount doesnt work anymore for me. This patch fixes at least udp nfs mounts. tcp does still hang. client and server is 2.6. --- /dev/shm/bindresvport.c 2003-12-08 02:33:24.000000000 +0100 +++ klibc/inet/bindresvport.c 2004-01-06 21:05:02.283779072 +0100 @@ -23,7 +23,7 @@ int bindresvport(int sd, struct sockaddr if (sin == NULL) { sin = &me;

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

Hi, When mounting a NFS share and an error occurs for some reason, the NFS share is not unmounted correctly: the local path is used instead of the remote path in the umount_v[23]() call. This patch fixes this. I found this while debugging some problems mounting the root file system on NFS in a test system; I saw this in the logs (/mnt/duplicated is the legitimate remote path): Jun 21

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

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

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(-)

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: 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

Commit-ID: b4f1a2bfe64cd0d8dc58c0b7173745f3c1af0bb3 Gitweb: http://git.kernel.org/?p=libs/klibc/klibc.git;a=commit;h=b4f1a2bfe64cd0d8dc58c0b7173745f3c1af0bb3 Author: Ben Hutchings <ben at decadent.org.uk> AuthorDate: Sat, 28 Mar 2020 22:17:36 +0000 Committer: Ben Hutchings <ben at decadent.org.uk> CommitDate: Sat, 28 Mar 2020 22:33:26 +0000 [klibc] nfsmount: Fix alignment of

-fcommon is not default anymore, with GCC 10 you get the following failure without it: KLIBCLD usr/klibc/libc.so ppc-linux-ld: usr/klibc/globals.o:/root/packages/klibc-2.0.7/usr/klibc/../include/unistd.h:15: multiple definition of `environ'; usr/klibc/__shared_init.o:/root/ldb_base/ofl/packages/klibc-2.0.7/usr/klibc/libc_init.c:42: first defined here ppc-linux-ld:

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

Hi, The following set of patches is intended mostly to improve ipconfig and nfsmount compatibility with glibc. The context: I'm working on yaird, an alternative to mkinitrd, and currently implementing nfs root file systems. This is based on ipconfig and nfsmount from klibc, with a rewritten version of kinit. Users should be able to build the package with vanilla glibc, since klibc is not

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:

I think I got it. Both nfsmount and `mount -t nfs` now default to rsize/wsize = 1 MB. By lowering this to 32K, all issues are gone, even with the default timeo=7. And nfsroot=xxx client responsiveness is a whole lot better. I think when nfsmount was initially written, the default rsize/wsize were much lower, which matched the timeo=7. Now they cause the lags/timeouts that I reported. So

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 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