From: Salvatore Bonaccorso <carnil@debian.org>
To: Sergio.Gelato@astro.su.se, Steve Dickson <steved@redhat.com>
Cc: Kevin Coffman <kwc@citi.umich.edu>, Neil Brown <neilb@suse.de>,
"linux-nfs@vger.kernel.org" <linux-nfs@vger.kernel.org>
Subject: Re: rpc.idmapd runs out of file descriptors
Date: Mon, 16 Sep 2024 19:19:58 +0200 [thread overview]
Message-ID: <ZuhovpK7Xhkuu3h9@eldamar.lan> (raw)
In-Reply-To: <ZuhR1bpMZmDWsNew@eldamar.lan>
Hi all,
On Mon, Sep 16, 2024 at 05:42:13PM +0200, Salvatore Bonaccorso wrote:
> Hi all,
>
> On Mon, Sep 16, 2024 at 02:28:50PM +0200, Sergio.Gelato@astro.su.se wrote:
> > On Mon, Sep 16, 2024 at 01:54:35PM +0200, Steve Dickson wrote:
> > > It did because it was not in the appropriate format... The patch
> > > was an attachment, not in-line, no Signed-off-by: line and
> > > the patch was not create by git format-patch command (which
> > > adds PATCH in the subject line).
> >
> > I see no mention of formatting requirements at
> > https://www.linux-nfs.org/wiki/index.php/Reporting_bugs
> > (not even by reference to the Linux kernel tree).
>
> Thank you all for looking into it. Steve, do you need to have it
> re-submitted in a git format-patch format? At least a Signed-off-by
> line by Sergio would be needed in my understanding.
I guess otherwise we can use soemthing like the following though a
Signed-off-by is probably not right here, or is it enough if I say
Reported-by: and Patch-originally-by: although the later is not an
official kernel doc mentioned tag?
Regards,
Salvatore
From 997981dd8d2b5977dd4cd54dab59de4ee3f57725 Mon Sep 17 00:00:00 2001
From: Sergio Gelato <Sergio.Gelato@astro.su.se>
Date: Tue, 4 Jun 2024 16:02:59 +0200
Subject: [PATCH] rpc.idmapd: nfsopen() failures should not be fatal
dirscancb() loops over all clnt* subdirectories of /run/rpc_pipefs/nfs/.
Some of these directories contain /idmap files, others don't. nfsopen()
returns -1 for the latter; we then want to skip the directory, not abort
the entire scan.
Reported-by: Sergio Gelato <sergio.gelato@astro.su.se>
Patch-originally-by: Sergio Gelato <sergio.gelato@astro.su.se>
Link: https://lore.kernel.org/linux-nfs/ZmCB_zqdu2cynJ1M@astro.su.se/
Link: https:/bugs.debian.org/1072573
Signed-off-by: Salvatore Bonaccorso <carnil@debian.org>
---
utils/idmapd/idmapd.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/utils/idmapd/idmapd.c b/utils/idmapd/idmapd.c
index cd9a965f8fbc..5231f56d24a8 100644
--- a/utils/idmapd/idmapd.c
+++ b/utils/idmapd/idmapd.c
@@ -556,7 +556,7 @@ dirscancb(int fd, short UNUSED(which), void *data)
if (nfsopen(ic) == -1) {
close(ic->ic_dirfd);
free(ic);
- goto out;
+ continue;
}
if (verbose > 2)
--
2.45.2
next prev parent reply other threads:[~2024-09-16 17:20 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-05 15:19 rpc.idmapd runs out of file descriptors Sergio Gelato
2024-09-14 7:29 ` Salvatore Bonaccorso
2024-09-16 0:04 ` NeilBrown
2024-09-16 11:54 ` Steve Dickson
2024-09-16 12:28 ` Sergio.Gelato
2024-09-16 15:42 ` Salvatore Bonaccorso
2024-09-16 17:19 ` Salvatore Bonaccorso [this message]
2024-09-16 18:18 ` Salvatore Bonaccorso
2024-09-17 7:06 ` Sergio.Gelato
2024-09-21 18:42 ` Steve Dickson
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=ZuhovpK7Xhkuu3h9@eldamar.lan \
--to=carnil@debian.org \
--cc=Sergio.Gelato@astro.su.se \
--cc=kwc@citi.umich.edu \
--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