Received: by 2002:a05:6a10:af89:0:0:0:0 with SMTP id iu9csp1362800pxb; Fri, 21 Jan 2022 16:33:33 -0800 (PST) X-Google-Smtp-Source: ABdhPJzP0VeXQIkHk7qRSac15M3006AQ+2ndXu6k7sTpcvQcsCc2FmdM8enzOIXjtBaWQP26wNNs X-Received: by 2002:a05:6a00:22d1:b0:4c2:5a55:960e with SMTP id f17-20020a056a0022d100b004c25a55960emr5900739pfj.74.1642811613229; Fri, 21 Jan 2022 16:33:33 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1642811613; cv=none; d=google.com; s=arc-20160816; b=mnO/rOFI+TniwNacwoooJGrypWqCCWmd1hxcUiMneGGALDofdY4ekZQUKygN0fot/K biiHJYCRBwdfudYoItNXDjgUyYjn1Mwkz8S+J9kbFsmHaSoVO7wItzm9mg9F+GBbPuqZ bypSa/e5vsPctBOMPboW3IyJi4y+L1qL2RFHVAwVNdWAOaT7qZlR6z8dKLE68aoohQ4X 48z6vBMiXR/aKSxn2iAk/FxJsu9S/ge3Zc5ulVKfbSWZx6Id+yY5csw4hg8sxzZvluPj vEaO9RPnN0oWpJyKDv0qZs7n6t2TmiGZa/NDfYETlMMV1TOJN5QhK+4Z7whkWke1B0uP Lr6Q== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:in-reply-to:content-disposition:mime-version :references:reply-to:message-id:subject:cc:to:from:date :dkim-signature:dkim-signature; bh=5Qrw2tBXZw6BLb51GobWaXyO72dke3+oxt8WFKSSsdI=; b=rhqsIbDpQie/FJAGWDAMuGNKJstGZrAVOzJafA/kEnJxm5YbCyjry9FCSyAj3OvL6i VyY8ZkRtkFGA3sL46BoQ7wV3JuEnkeKLQplvUK1N6NnVX8rlWfIyRQrm9MkEUgE0KT91 t01rcd47LZg1wd+cRxsVnwtVS0cq7mjktq22l5guc0mNc9NP8nHfdMQfMCTORpC/KFYH sUISqLrsctpc7rr5s5bm8yttEE2lT9BSFN0UnhaVlP1WVz8fNid30l8+npoTeMnG8YNq XH/JwFvmiscrpi8+NNPDIg6kmH4IQu/507glyCtuRxDxLBVkLHEkVDkhv0ClSTB7I9hc 0ZgQ== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@suse.cz header.s=susede2_rsa header.b=K042C3kc; dkim=neutral (no key) header.i=@suse.cz header.b=SuSVz97N; spf=pass (google.com: domain of linux-nfs-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-nfs-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id 145si7523836pga.75.2022.01.21.16.33.20; Fri, 21 Jan 2022 16:33:33 -0800 (PST) Received-SPF: pass (google.com: domain of linux-nfs-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18; Authentication-Results: mx.google.com; dkim=pass header.i=@suse.cz header.s=susede2_rsa header.b=K042C3kc; dkim=neutral (no key) header.i=@suse.cz header.b=SuSVz97N; spf=pass (google.com: domain of linux-nfs-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-nfs-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1348556AbiAUFaH (ORCPT + 99 others); Fri, 21 Jan 2022 00:30:07 -0500 Received: from smtp-out2.suse.de ([195.135.220.29]:45682 "EHLO smtp-out2.suse.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1348719AbiAUF36 (ORCPT ); Fri, 21 Jan 2022 00:29:58 -0500 Received: from imap2.suse-dmz.suse.de (imap2.suse-dmz.suse.de [192.168.254.74]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature ECDSA (P-521) server-digest SHA512) (No client certificate requested) by smtp-out2.suse.de (Postfix) with ESMTPS id 3CC3B1F395; Fri, 21 Jan 2022 05:29:57 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=suse.cz; s=susede2_rsa; t=1642742997; h=from:from:reply-to:reply-to:date:date:message-id:message-id:to:to: cc:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=5Qrw2tBXZw6BLb51GobWaXyO72dke3+oxt8WFKSSsdI=; b=K042C3kcNuCBQxUvzEQgw+gNVNf+M6JJQi9ggO3WMMgOCiiU4TKvKoB3sVeinWbuvlTEqN 8x8WRrXKetlPU6JEQmsJ1XkRbIZ76PugBlPL07dtMPqlr9d9UdeqAcUepxa+EUrTgH2jcp zGGfjDQmC2R6XhVAogCo1f49Vc24+hE= DKIM-Signature: v=1; a=ed25519-sha256; c=relaxed/relaxed; d=suse.cz; s=susede2_ed25519; t=1642742997; h=from:from:reply-to:reply-to:date:date:message-id:message-id:to:to: cc:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=5Qrw2tBXZw6BLb51GobWaXyO72dke3+oxt8WFKSSsdI=; b=SuSVz97N0JBfHOdVfNxRYhsadDJnh2l2udOIbpj3Ssl0I3jzBzWZhur/xow6N4Cn1LWU8S sqlhn+O+iNUG3CCQ== Received: from imap2.suse-dmz.suse.de (imap2.suse-dmz.suse.de [192.168.254.74]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature ECDSA (P-521) server-digest SHA512) (No client certificate requested) by imap2.suse-dmz.suse.de (Postfix) with ESMTPS id E8255139C3; Fri, 21 Jan 2022 05:29:56 +0000 (UTC) Received: from dovecot-director2.suse.de ([192.168.254.65]) by imap2.suse-dmz.suse.de with ESMTPSA id SqeuNtRE6mFgdgAAMHmgww (envelope-from ); Fri, 21 Jan 2022 05:29:56 +0000 Date: Fri, 21 Jan 2022 06:29:55 +0100 From: Petr Vorel To: Nikita Yushchenko Cc: ltp@lists.linux.it, kernel@openvz.org, linux-nfs@vger.kernel.org, Steve Dickson , NeilBrown Subject: Re: [PATCH] rpc_lib.sh: fix portmapper detection in case of socket activation Message-ID: Reply-To: Petr Vorel References: <20220120143727.27057-1-nikita.yushchenko@virtuozzo.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: Precedence: bulk List-ID: X-Mailing-List: linux-nfs@vger.kernel.org Hi Nikita, > 21.01.2022 00:01, Petr Vorel wrote: > > Hi Nikita, > > [ Cc: Steve as user-space maintainer, also Neil and whole linux-nfs ] > > > On systemd-based linux hosts, rpcbind service is typically started via > > > socket activation, when the first client connects. If no client has > > > connected before LTP rpc test starts, rpcbind process will not be > > > running at the time of check_portmap_rpcbind() execution, causing > > > check_portmap_rpcbind() to report TCONF error. > > > Fix that by adding a quiet invocation of 'rpcinfo' before checking for > > > rpcbind. > > Looks reasonable, but I'd prefer to have confirmation from NFS experts. > NFS is not involved here, this is about sunrpc tests. Sure. Just tirpc (in libtirpc or the the old SUN-RPC already removed from glibc) are used in NFS. Steve is the libtirpc maintainer. > I had to add this patch to make 'runltp -f net.rpc' pass just after > container is started - that happens in container autotests here. Yep, I suspected this. Because on normal linux distro it's working right after boot (tested on rpc01.sh). Can't this be a setup issue? Kind regards, Petr > Nikita