From: Petr Vorel <pvorel@suse.cz>
To: NeilBrown <neilb@suse.de>, Steve Dickson <steved@redhat.com>,
linux-nfs@vger.kernel.org
Subject: Abstract address for rpcbind in kernel not working
Date: Mon, 16 Dec 2024 21:26:54 +0100 [thread overview]
Message-ID: <20241216202654.GA619856@pevik> (raw)
Hi Neil, Steve,
some time ago I reported a problem with nfslock01.sh test on NFSv3 [1].
Neil send various fixes to support abstract address for rpcbind in kernel:
* kernel [2] released in v6.5-rc1 as:
4388ce05fa38 ("SUNRPC: support abstract unix socket addresses")
626590ea4c93 ("SUNRPC: attempt to reach rpcbind with an abstract socket name")
* libtirpc [3] released in 1.3.5
d4d6c80 ("Allow working with abstract AF_UNIX addresses.")
33c687b ("Change local_rpcb() to take a targaddr pointer.")
d68523a ("Try using a new abstract address when connecting to rpcbind")
* rpcbind [4] released in 1.2.7
4e1f1b2 ("rpcinfo: try connecting using abstract address.")
652aa9a ("Listen on an AF_UNIX abstract address if supported.")
NOTE: these 2 patches were never merged
[PATCH 1/4] anpage: describe use of extra port for broadcast rpc [5]
[PATCH 2/4] rpcbind: allow broadcast RPC to be disabled. [6]
But when testing nfslock01.sh with:
$ rpm -q -e libtirpc3 -e rpcbind
libtirpc3-1.3.6-1.1.x86_64
rpcbind-1.2.7-1.1.x86_64
$ uname -a
Linux ts 6.13.0-rc1-1.g492f944-default #1 SMP PREEMPT_DYNAMIC Mon Dec 2 08:55:00 UTC 2024 (492f944) x86_64 x86_64 x86_64 GNU/Linux
it's still not working. Any hint what's wrong?
Kind regards,
Petr
dmesg:
[501926.369717] [ T28210] lockd: cannot monitor 10.0.0.2
[501926.372490] [ T28211] lockd: cannot monitor 10.0.0.2
$ cat /usr/lib/systemd/system/rpcbind.socket
[Unit]
Description=RPCbind Server Activation Socket
DefaultDependencies=no
Wants=rpcbind.target
Before=rpcbind.target
[Socket]
ListenStream=/run/rpcbind.sock
ListenStream=@/run/rpcbind.sock
# RPC netconfig can't handle ipv6/ipv4 dual sockets
BindIPv6Only=ipv6-only
ListenStream=0.0.0.0:111
ListenDatagram=0.0.0.0:111
ListenStream=[::]:111
ListenDatagram=[::]:111
[Install]
WantedBy=sockets.target
# PATH="/opt/ltp/testcases/bin:$PATH" nfslock01.sh -v 3 -t tcp
nfslock01 1 TINFO: Running: nfslock01.sh -v 3 -t tcp
nfslock01 1 TINFO: Tested kernel: Linux ts 6.13.0-rc1-1.g492f944-default #1 SMP PREEMPT_DYNAMIC Mon Dec 2 08:55:00 UTC 2024 (492f944) x86_64 x86_64 x86_64 GNU/Linux
nfslock01 1 TINFO: initialize 'lhost' 'ltp_ns_veth2' interface
nfslock01 1 TINFO: add local addr 10.0.0.2/24
nfslock01 1 TINFO: add local addr fd00:1:1:1::2/64
nfslock01 1 TINFO: initialize 'rhost' 'ltp_ns_veth1' interface
nfslock01 1 TINFO: add remote addr 10.0.0.1/24
nfslock01 1 TINFO: add remote addr fd00:1:1:1::1/64
nfslock01 1 TINFO: Network config (local -- remote):
nfslock01 1 TINFO: ltp_ns_veth2 -- ltp_ns_veth1
nfslock01 1 TINFO: 10.0.0.2/24 -- 10.0.0.1/24
nfslock01 1 TINFO: fd00:1:1:1::2/64 -- fd00:1:1:1::1/64
nfslock01 1 TINFO: Using /tmp/LTP_nfslock01.cXBE0JezwN as tmpdir (tmpfs filesystem)
tst_device.c:96: TINFO: Found free device 0 '/dev/loop0'
tst_supported_fs_types.c:169: TINFO: Skipping ext2 as requested by the test
tst_supported_fs_types.c:169: TINFO: Skipping ext3 as requested by the test
tst_supported_fs_types.c:97: TINFO: Kernel supports ext4
tst_supported_fs_types.c:62: TINFO: mkfs.ext4 does exist
tst_supported_fs_types.c:97: TINFO: Kernel supports xfs
tst_supported_fs_types.c:62: TINFO: mkfs.xfs does exist
tst_supported_fs_types.c:97: TINFO: Kernel supports btrfs
tst_supported_fs_types.c:62: TINFO: mkfs.btrfs does exist
tst_supported_fs_types.c:97: TINFO: Kernel supports bcachefs
tst_supported_fs_types.c:62: TINFO: mkfs.bcachefs does exist
tst_supported_fs_types.c:169: TINFO: Skipping vfat as requested by the test
tst_supported_fs_types.c:169: TINFO: Skipping exfat as requested by the test
tst_supported_fs_types.c:169: TINFO: Skipping ntfs as requested by the test
tst_supported_fs_types.c:169: TINFO: Skipping tmpfs as requested by the test
nfslock01 1 TINFO: === Testing on ext4 ===
nfslock01 1 TINFO: Formatting ext4 with opts='/dev/loop0'
nfslock01 1 TINFO: Mounting device: mount -t ext4 /dev/loop0 /tmp/LTP_nfslock01.cXBE0JezwN/mntpoint
nfslock01 1 TINFO: timeout per run is 0h 5m 0s
nfslock01 1 TINFO: mount.nfs: (linux nfs-utils 2.6.4)
nfslock01 1 TINFO: setup NFSv3, socket type tcp
nfslock01 1 TINFO: Mounting /tmp/LTP_nfslock01.cXBE0JezwN/3/0
nfslock01 1 TINFO: Mounting NFS: mount -v -t nfs -o proto=tcp,vers=3 10.0.0.2:/tmp/LTP_nfslock01.cXBE0JezwN/mntpoint/3/tcp /tmp/LTP_nfslock01.cXBE0JezwN/3/0
nfslock01 1 TINFO: creating test files (chars: 64, lines: 16384)
nfslock01 1 TINFO: Testing locking
nfslock01 1 TINFO: locking 'flock_idata' file and writing data
nfslock01 1 failed in writeb_lock, errno = 37
TINFO: waiting for pids: 27919 27920
failed in writeb_lock, errno = 37
nfslock01 1 TFAIL: nfs_lock process failed
nfslock01 2 TINFO: Cleaning up testcase
nfslock01 2 TINFO: Unmounting /tmp/LTP_nfslock01.cXBE0JezwN/3/0
nfslock01 2 TINFO: === Testing on xfs ===
nfslock01 2 TINFO: Formatting xfs with opts='/dev/loop0'
nfslock01 2 TINFO: Mounting device: mount -t xfs /dev/loop0 /tmp/LTP_nfslock01.cXBE0JezwN/mntpoint
nfslock01 2 TINFO: timeout per run is 0h 5m 0s
nfslock01 2 TINFO: mount.nfs: (linux nfs-utils 2.6.4)
nfslock01 2 TINFO: setup NFSv3, socket type tcp
nfslock01 2 TINFO: Mounting /tmp/LTP_nfslock01.cXBE0JezwN/3/0
nfslock01 2 TINFO: Mounting NFS: mount -v -t nfs -o proto=tcp,vers=3 10.0.0.2:/tmp/LTP_nfslock01.cXBE0JezwN/mntpoint/3/tcp /tmp/LTP_nfslock01.cXBE0JezwN/3/0
nfslock01 2 TINFO: creating test files (chars: 64, lines: 16384)
nfslock01 2 TINFO: Testing locking
nfslock01 2 TINFO: locking 'flock_idata' file and writing data
nfslock01 2 failed in writeb_lock, errno = 37
TINFO: waiting for pids: 28005 28006
nfslock01 2 TFAIL: failed in writeb_lock, errno = 37
nfs_lock process failed
nfslock01 3 TINFO: Cleaning up testcase
nfslock01 3 TINFO: Unmounting /tmp/LTP_nfslock01.cXBE0JezwN/3/0
nfslock01 3 TINFO: === Testing on btrfs ===
nfslock01 3 TINFO: Formatting btrfs with opts='/dev/loop0'
nfslock01 3 TINFO: Mounting device: mount -t btrfs /dev/loop0 /tmp/LTP_nfslock01.cXBE0JezwN/mntpoint
nfslock01 3 TINFO: timeout per run is 0h 5m 0s
nfslock01 3 TINFO: mount.nfs: (linux nfs-utils 2.6.4)
nfslock01 3 TINFO: setup NFSv3, socket type tcp
nfslock01 3 TINFO: Mounting /tmp/LTP_nfslock01.cXBE0JezwN/3/0
nfslock01 3 TINFO: Mounting NFS: mount -v -t nfs -o proto=tcp,vers=3 10.0.0.2:/tmp/LTP_nfslock01.cXBE0JezwN/mntpoint/3/tcp /tmp/LTP_nfslock01.cXBE0JezwN/3/0
nfslock01 3 TINFO: creating test files (chars: 64, lines: 16384)
nfslock01 3 TINFO: Testing locking
nfslock01 3 TINFO: locking 'flock_idata' file and writing data
nfslock01 3 TINFO: waiting for pids: 28103 28104
failed in writeb_lock, errno = 37
failed in writeb_lock, errno = 37
nfslock01 3 TFAIL: nfs_lock process failed
nfslock01 4 TINFO: Cleaning up testcase
nfslock01 4 TINFO: Unmounting /tmp/LTP_nfslock01.cXBE0JezwN/3/0
nfslock01 4 TINFO: === Testing on bcachefs ===
nfslock01 4 TINFO: Formatting bcachefs with opts='/dev/loop0'
nfslock01 4 TINFO: Mounting device: mount -t bcachefs /dev/loop0 /tmp/LTP_nfslock01.cXBE0JezwN/mntpoint
nfslock01 4 TINFO: timeout per run is 0h 5m 0s
nfslock01 4 TINFO: mount.nfs: (linux nfs-utils 2.6.4)
nfslock01 4 TINFO: setup NFSv3, socket type tcp
nfslock01 4 TINFO: Mounting /tmp/LTP_nfslock01.cXBE0JezwN/3/0
nfslock01 4 TINFO: Mounting NFS: mount -v -t nfs -o proto=tcp,vers=3 10.0.0.2:/tmp/LTP_nfslock01.cXBE0JezwN/mntpoint/3/tcp /tmp/LTP_nfslock01.cXBE0JezwN/3/0
nfslock01 4 TINFO: creating test files (chars: 64, lines: 16384)
nfslock01 4 TINFO: Testing locking
nfslock01 4 TINFO: locking 'flock_idata' file and writing data
nfslock01 4 TINFO: failed in writeb_lock, errno = 37
failed in writeb_lock, errno = 37
waiting for pids: 28210 28211
nfslock01 4 TFAIL: nfs_lock process failed
nfslock01 5 TINFO: Cleaning up testcase
nfslock01 5 TINFO: Unmounting /tmp/LTP_nfslock01.cXBE0JezwN/3/0
nfslock01 5 TINFO: AppArmor enabled, this may affect test results
nfslock01 5 TINFO: it can be disabled with TST_DISABLE_APPARMOR=1 (requires super/root)
nfslock01 5 TINFO: loaded AppArmor profiles: none
Summary:
passed 0
failed 4
broken 0
skipped 0
warnings 0
[1] https://lore.kernel.org/linux-nfs/20230502075921.3614794-1-pvorel@suse.cz/
[2] https://lore.kernel.org/linux-nfs/168375610447.26246.3237443941479930060.stgit@noble.brown/
[3] https://lore.kernel.org/linux-nfs/20240311014327.19692-1-neilb@suse.de/
[4] https://lore.kernel.org/linux-nfs/20240225235628.12473-1-neilb@suse.de/
[5] https://lore.kernel.org/linux-nfs/20240225235628.12473-2-neilb@suse.de/
[6] https://lore.kernel.org/linux-nfs/20240225235628.12473-3-neilb@suse.de/
reply other threads:[~2024-12-16 20:27 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20241216202654.GA619856@pevik \
--to=pvorel@suse.cz \
--cc=linux-nfs@vger.kernel.org \
--cc=neilb@suse.de \
--cc=steved@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox