[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <55f1ff08-fc3c-62ed-429d-c9ae285a3a49@embeddedor.com>
Date: Tue, 15 Sep 2020 18:51:41 -0500
From: "Gustavo A. R. Silva" <gustavo@...eddedor.com>
To: Joe Perches <joe@...ches.com>,
Nick Desaulniers <ndesaulniers@...gle.com>,
Trond Myklebust <trond.myklebust@...merspace.com>,
Anna Schumaker <anna.schumaker@...app.com>
Cc: Nathan Chancellor <natechancellor@...il.com>,
Miaohe Lin <linmiaohe@...wei.com>,
Hongxiang Lou <louhongxiang@...wei.com>,
linux-nfs@...r.kernel.org, linux-kernel@...r.kernel.org,
clang-built-linux@...glegroups.com
Subject: Re: [PATCH] nfs: remove incorrect fallthrough label
On 9/15/20 18:29, Joe Perches wrote:
> On Tue, 2020-09-15 at 15:57 -0700, Nick Desaulniers wrote:
>> There is no case after the default from which to fallthrough to. Clang
>> will error in this case (unhelpfully without context, see link below)
>> and GCC will with -Wswitch-unreachable.
>>
>> The previous commit should have just removed the comment.
> []
>> diff --git a/fs/nfs/super.c b/fs/nfs/super.c
> []
>> @@ -889,7 +889,6 @@ static struct nfs_server *nfs_try_mount_request(struct fs_context *fc)
>> default:
>> if (rpcauth_get_gssinfo(flavor, &info) != 0)
>> continue;
>> - fallthrough;
>
> My preference would be to convert the fallthrough
> to a break here so if someone ever adds another
> label after default: for any reason, the code would
> still work as expected.
I agree with Joe.
Thanks
--
Gustavo
Powered by blists - more mailing lists