* [PATCH -next] NFSD: make symbol 'nfsd_notifier_lock' static
@ 2021-11-30 11:34 Wei Yongjun
2021-11-30 20:19 ` Chuck Lever III
0 siblings, 1 reply; 6+ messages in thread
From: Wei Yongjun @ 2021-11-30 11:34 UTC (permalink / raw)
To: weiyongjun1, NeilBrown, J. Bruce Fields, Chuck Lever
Cc: linux-nfs, kernel-janitors, Hulk Robot
The sparse tool complains as follows:
fs/nfsd/nfssvc.c:437:1: warning:
symbol 'nfsd_notifier_lock' was not declared. Should it be static?
This symbol is not used outside of nfssvc.c, so marks it static.
Fixes: 6ac25fbcbde9 ("NFSD: simplify locking for network notifier.")
Reported-by: Hulk Robot <hulkci@huawei.com>
Signed-off-by: Wei Yongjun <weiyongjun1@huawei.com>
---
fs/nfsd/nfssvc.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/fs/nfsd/nfssvc.c b/fs/nfsd/nfssvc.c
index 070525fbc1ad..14c1ef6f8cc7 100644
--- a/fs/nfsd/nfssvc.c
+++ b/fs/nfsd/nfssvc.c
@@ -434,7 +434,7 @@ static void nfsd_shutdown_net(struct net *net)
nfsd_shutdown_generic();
}
-DEFINE_SPINLOCK(nfsd_notifier_lock);
+static DEFINE_SPINLOCK(nfsd_notifier_lock);
static int nfsd_inetaddr_event(struct notifier_block *this, unsigned long event,
void *ptr)
{
^ permalink raw reply related [flat|nested] 6+ messages in thread
* Re: [PATCH -next] NFSD: make symbol 'nfsd_notifier_lock' static
2021-11-30 11:34 [PATCH -next] NFSD: make symbol 'nfsd_notifier_lock' static Wei Yongjun
@ 2021-11-30 20:19 ` Chuck Lever III
2021-12-03 11:25 ` Dan Carpenter
0 siblings, 1 reply; 6+ messages in thread
From: Chuck Lever III @ 2021-11-30 20:19 UTC (permalink / raw)
To: Wei Yongjun
Cc: Neil Brown, Bruce Fields, Linux NFS Mailing List,
kernel-janitors@vger.kernel.org, Hulk Robot
> On Nov 30, 2021, at 6:34 AM, Wei Yongjun <weiyongjun1@huawei.com> wrote:
>
> The sparse tool complains as follows:
>
> fs/nfsd/nfssvc.c:437:1: warning:
> symbol 'nfsd_notifier_lock' was not declared. Should it be static?
>
> This symbol is not used outside of nfssvc.c, so marks it static.
>
> Fixes: 6ac25fbcbde9 ("NFSD: simplify locking for network notifier.")
> Reported-by: Hulk Robot <hulkci@huawei.com>
> Signed-off-by: Wei Yongjun <weiyongjun1@huawei.com>
> ---
> fs/nfsd/nfssvc.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/fs/nfsd/nfssvc.c b/fs/nfsd/nfssvc.c
> index 070525fbc1ad..14c1ef6f8cc7 100644
> --- a/fs/nfsd/nfssvc.c
> +++ b/fs/nfsd/nfssvc.c
> @@ -434,7 +434,7 @@ static void nfsd_shutdown_net(struct net *net)
> nfsd_shutdown_generic();
> }
>
> -DEFINE_SPINLOCK(nfsd_notifier_lock);
> +static DEFINE_SPINLOCK(nfsd_notifier_lock);
> static int nfsd_inetaddr_event(struct notifier_block *this, unsigned long event,
> void *ptr)
> {
>
Thanks! This was pushed to the tip of the for-next branch at
https://git.kernel.org/pub/scm/linux/kernel/git/cel/linux.git
I removed the Fixes: line because a backport is unnecessary, and
the commit ID is not yet permanent.
--
Chuck Lever
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: [PATCH -next] NFSD: make symbol 'nfsd_notifier_lock' static
2021-11-30 20:19 ` Chuck Lever III
@ 2021-12-03 11:25 ` Dan Carpenter
2021-12-03 15:17 ` Chuck Lever III
0 siblings, 1 reply; 6+ messages in thread
From: Dan Carpenter @ 2021-12-03 11:25 UTC (permalink / raw)
To: Chuck Lever III
Cc: Wei Yongjun, Neil Brown, Bruce Fields, Linux NFS Mailing List,
kernel-janitors@vger.kernel.org, Hulk Robot
On Tue, Nov 30, 2021 at 08:19:47PM +0000, Chuck Lever III wrote:
> >
> > -DEFINE_SPINLOCK(nfsd_notifier_lock);
> > +static DEFINE_SPINLOCK(nfsd_notifier_lock);
> > static int nfsd_inetaddr_event(struct notifier_block *this, unsigned long event,
> > void *ptr)
> > {
> >
>
> Thanks! This was pushed to the tip of the for-next branch at
>
> https://git.kernel.org/pub/scm/linux/kernel/git/cel/linux.git
>
> I removed the Fixes: line because a backport is unnecessary, and
> the commit ID is not yet permanent.
Removing the tag, makes it more complicated for backporters. Before
they could tell automatically from the Fixes tag that backporting was
not necessary.
On the other hand, does this patch really need a Fixes tag since it's
not a runtime bug? Different maintainers take different sides in that
argument.
If the patch needed a fixes tag then a lot of maintainers have scripts
to update the tag during a rebase. There are also automated tool run on
linux-next which emails a warning when the Fixes tags point to an
invalid hash.
regards,
dan carpenter
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: [PATCH -next] NFSD: make symbol 'nfsd_notifier_lock' static
2021-12-03 11:25 ` Dan Carpenter
@ 2021-12-03 15:17 ` Chuck Lever III
2021-12-03 15:19 ` Bruce Fields
0 siblings, 1 reply; 6+ messages in thread
From: Chuck Lever III @ 2021-12-03 15:17 UTC (permalink / raw)
To: Dan Carpenter
Cc: Wei Yongjun, Neil Brown, Bruce Fields, Linux NFS Mailing List,
kernel-janitors@vger.kernel.org, Hulk Robot
> On Dec 3, 2021, at 6:25 AM, Dan Carpenter <dan.carpenter@oracle.com> wrote:
>
> On Tue, Nov 30, 2021 at 08:19:47PM +0000, Chuck Lever III wrote:
>>>
>>> -DEFINE_SPINLOCK(nfsd_notifier_lock);
>>> +static DEFINE_SPINLOCK(nfsd_notifier_lock);
>>> static int nfsd_inetaddr_event(struct notifier_block *this, unsigned long event,
>>> void *ptr)
>>> {
>>>
>>
>> Thanks! This was pushed to the tip of the for-next branch at
>>
>> https://git.kernel.org/pub/scm/linux/kernel/git/cel/linux.git
>>
>> I removed the Fixes: line because a backport is unnecessary, and
>> the commit ID is not yet permanent.
>
> Removing the tag, makes it more complicated for backporters. Before
> they could tell automatically from the Fixes tag that backporting was
> not necessary.
>
> On the other hand, does this patch really need a Fixes tag since it's
> not a runtime bug? Different maintainers take different sides in that
> argument.
>
> If the patch needed a fixes tag then a lot of maintainers have scripts
> to update the tag during a rebase. There are also automated tool run on
> linux-next which emails a warning when the Fixes tags point to an
> invalid hash.
Hi Dan, the patch fixes a bug in my for-next branch, not in mainline.
There's really no need for a Fixes: tag.
--
Chuck Lever
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: [PATCH -next] NFSD: make symbol 'nfsd_notifier_lock' static
2021-12-03 15:17 ` Chuck Lever III
@ 2021-12-03 15:19 ` Bruce Fields
2021-12-03 15:28 ` Chuck Lever III
0 siblings, 1 reply; 6+ messages in thread
From: Bruce Fields @ 2021-12-03 15:19 UTC (permalink / raw)
To: Chuck Lever III
Cc: Dan Carpenter, Wei Yongjun, Neil Brown, Linux NFS Mailing List,
kernel-janitors@vger.kernel.org, Hulk Robot
On Fri, Dec 03, 2021 at 03:17:30PM +0000, Chuck Lever III wrote:
>
>
> > On Dec 3, 2021, at 6:25 AM, Dan Carpenter <dan.carpenter@oracle.com> wrote:
> >
> > On Tue, Nov 30, 2021 at 08:19:47PM +0000, Chuck Lever III wrote:
> >>>
> >>> -DEFINE_SPINLOCK(nfsd_notifier_lock);
> >>> +static DEFINE_SPINLOCK(nfsd_notifier_lock);
> >>> static int nfsd_inetaddr_event(struct notifier_block *this, unsigned long event,
> >>> void *ptr)
> >>> {
> >>>
> >>
> >> Thanks! This was pushed to the tip of the for-next branch at
> >>
> >> https://git.kernel.org/pub/scm/linux/kernel/git/cel/linux.git
> >>
> >> I removed the Fixes: line because a backport is unnecessary, and
> >> the commit ID is not yet permanent.
> >
> > Removing the tag, makes it more complicated for backporters. Before
> > they could tell automatically from the Fixes tag that backporting was
> > not necessary.
> >
> > On the other hand, does this patch really need a Fixes tag since it's
> > not a runtime bug? Different maintainers take different sides in that
> > argument.
> >
> > If the patch needed a fixes tag then a lot of maintainers have scripts
> > to update the tag during a rebase. There are also automated tool run on
> > linux-next which emails a warning when the Fixes tags point to an
> > invalid hash.
>
> Hi Dan, the patch fixes a bug in my for-next branch, not in mainline.
> There's really no need for a Fixes: tag.
Assuming it doesn't get folded into the fixed patch before going
upstream, it'd be useful information to have there.
--b.
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: [PATCH -next] NFSD: make symbol 'nfsd_notifier_lock' static
2021-12-03 15:19 ` Bruce Fields
@ 2021-12-03 15:28 ` Chuck Lever III
0 siblings, 0 replies; 6+ messages in thread
From: Chuck Lever III @ 2021-12-03 15:28 UTC (permalink / raw)
To: Bruce Fields
Cc: Dan Carpenter, Wei Yongjun, Neil Brown, Linux NFS Mailing List,
kernel-janitors@vger.kernel.org, Hulk Robot
> On Dec 3, 2021, at 10:19 AM, Bruce Fields <bfields@fieldses.org> wrote:
>
> On Fri, Dec 03, 2021 at 03:17:30PM +0000, Chuck Lever III wrote:
>>
>>
>>> On Dec 3, 2021, at 6:25 AM, Dan Carpenter <dan.carpenter@oracle.com> wrote:
>>>
>>> On Tue, Nov 30, 2021 at 08:19:47PM +0000, Chuck Lever III wrote:
>>>>>
>>>>> -DEFINE_SPINLOCK(nfsd_notifier_lock);
>>>>> +static DEFINE_SPINLOCK(nfsd_notifier_lock);
>>>>> static int nfsd_inetaddr_event(struct notifier_block *this, unsigned long event,
>>>>> void *ptr)
>>>>> {
>>>>>
>>>>
>>>> Thanks! This was pushed to the tip of the for-next branch at
>>>>
>>>> https://git.kernel.org/pub/scm/linux/kernel/git/cel/linux.git
>>>>
>>>> I removed the Fixes: line because a backport is unnecessary, and
>>>> the commit ID is not yet permanent.
>>>
>>> Removing the tag, makes it more complicated for backporters. Before
>>> they could tell automatically from the Fixes tag that backporting was
>>> not necessary.
>>>
>>> On the other hand, does this patch really need a Fixes tag since it's
>>> not a runtime bug? Different maintainers take different sides in that
>>> argument.
>>>
>>> If the patch needed a fixes tag then a lot of maintainers have scripts
>>> to update the tag during a rebase. There are also automated tool run on
>>> linux-next which emails a warning when the Fixes tags point to an
>>> invalid hash.
>>
>> Hi Dan, the patch fixes a bug in my for-next branch, not in mainline.
>> There's really no need for a Fixes: tag.
>
> Assuming it doesn't get folded into the fixed patch before going
> upstream, it'd be useful information to have there.
I'm sorry, but I don't see how that information is useful for a
fixing a patch that is in the same merge set. I'll fold it in.
--
Chuck Lever
^ permalink raw reply [flat|nested] 6+ messages in thread
end of thread, other threads:[~2021-12-03 15:28 UTC | newest]
Thread overview: 6+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2021-11-30 11:34 [PATCH -next] NFSD: make symbol 'nfsd_notifier_lock' static Wei Yongjun
2021-11-30 20:19 ` Chuck Lever III
2021-12-03 11:25 ` Dan Carpenter
2021-12-03 15:17 ` Chuck Lever III
2021-12-03 15:19 ` Bruce Fields
2021-12-03 15:28 ` Chuck Lever III
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.