On Tue, 8 Jul 2014 10:33:39 -0400
Steve Dickson <steved@xxxxxxxxxx> wrote:
> When there is no kernel modules loaded the rpc_pipefs
> directory is empty, which cause rpc.gssd to silently
> exit.
>
> This patch adds a check to see if the topdirs_list
> is empty. If so error out without dropping a core.
>
> Signed-off-by: Steve Dickson <steved@xxxxxxxxxx>
> ---
> utils/gssd/gssd_main_loop.c | 11 ++++++++---
> 1 file changed, 8 insertions(+), 3 deletions(-)
>
> diff --git a/utils/gssd/gssd_main_loop.c b/utils/gssd/gssd_main_loop.c
> index 9970028..6946ab6 100644
> --- a/utils/gssd/gssd_main_loop.c
> +++ b/utils/gssd/gssd_main_loop.c
> @@ -173,6 +173,10 @@ topdirs_init_list(void)
> if (ret)
> goto out_err;
> }
> + if (TAILQ_EMPTY(&topdirs_list)) {
> + printerr(0, "ERROR: rpc_pipefs directory '%s' is empty!\n", pipefs_dir);
> + return -1;
> + }
> closedir(pipedir);
> return 0;
> out_err:
> @@ -233,9 +237,10 @@ gssd_run()
> sigaddset(&set, DNOTIFY_SIGNAL);
> sigprocmask(SIG_UNBLOCK, &set, NULL);
>
> - if (topdirs_init_list() != 0)
> - return;
> -
> + if (topdirs_init_list() != 0) {
> + /* Error msg is already printed */
> + exit(1);
> + }
> init_client_list();
>
> printerr(1, "beginning poll\n");
Does it drop a core now? It looks sort of like it would just exit(1)
silently.
In any case, this patch is certainly better than crashing, but gssd
looks sort of like it's doing the wrong thing here. Should it not just
wait idly for directories to show up instead of exiting if none are
present?
Also, because topdir_init_list is run only once, it looks like gssd
doesn't properly handle the case where there may be some directories in
rpc_pipefs when gssd starts, but then others show up later. Any that
show up after gssd is started are just ignored currently, right? That
seems like a subtle source of bugs if you just happen to start gssd a
little early.
--
Jeff Layton <jlayton@xxxxxxxxxxxxxxx>
--
To unsubscribe from this list: send the line "unsubscribe linux-nfs" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
