From: Jakub Kicinski <kuba@kernel.org>
To: Chuck Lever III <chuck.lever@oracle.com>
Cc: Zhipeng Lu <alexious@zju.edu.cn>,
Jeff Layton <jlayton@kernel.org>, Neil Brown <neilb@suse.de>,
Olga Kornievskaia <kolga@netapp.com>,
Dai Ngo <dai.ngo@oracle.com>, Tom Talpey <tom@talpey.com>,
Trond Myklebust <trond.myklebust@hammerspace.com>,
Anna Schumaker <anna@kernel.org>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Paolo Abeni <pabeni@redhat.com>, Simo Sorce <simo@redhat.com>,
Steve Dickson <steved@redhat.com>,
Kevin Coffman <kwc@citi.umich.edu>,
Linux NFS Mailing List <linux-nfs@vger.kernel.org>,
"open list:NETWORKING [GENERAL]" <netdev@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] [v2] SUNRPC: fix a memleak in gss_import_v2_context
Date: Fri, 12 Jan 2024 12:01:27 -0800 [thread overview]
Message-ID: <20240112120127.5eee94f2@kernel.org> (raw)
In-Reply-To: <824EC6A8-24EA-4998-B1CB-8E54FBB51129@oracle.com>
On Fri, 12 Jan 2024 19:27:40 +0000 Chuck Lever III wrote:
> > cocci says:
> >
> > net/sunrpc/auth_gss/gss_krb5_mech.c:458:2-3: Unneeded semicolon
>
> I planned to take this patch via NFSD's "for v6.9" branch.
> I can remove that semicolon. Thanks!
Sorry for the lack of clarity, I wasn't intending to take it.
The patch did get into our checking machinery and the warning
was reported, so I figured why not say so on the list.
I'll mention the intentions more clearly next time!
next prev parent reply other threads:[~2024-01-12 20:01 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-12 8:45 [PATCH] [v2] SUNRPC: fix a memleak in gss_import_v2_context Zhipeng Lu
2024-01-12 13:23 ` Jeff Layton
2024-01-12 19:24 ` Jakub Kicinski
2024-01-12 19:27 ` Chuck Lever III
2024-01-12 20:01 ` Jakub Kicinski [this message]
2024-01-15 11:09 ` Simon Horman
2024-01-15 14:23 ` Chuck Lever III
2024-01-17 7:44 ` alexious
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=20240112120127.5eee94f2@kernel.org \
--to=kuba@kernel.org \
--cc=alexious@zju.edu.cn \
--cc=anna@kernel.org \
--cc=chuck.lever@oracle.com \
--cc=dai.ngo@oracle.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=jlayton@kernel.org \
--cc=kolga@netapp.com \
--cc=kwc@citi.umich.edu \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nfs@vger.kernel.org \
--cc=neilb@suse.de \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=simo@redhat.com \
--cc=steved@redhat.com \
--cc=tom@talpey.com \
--cc=trond.myklebust@hammerspace.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;
as well as URLs for NNTP newsgroup(s).