From: "J. Bruce Fields" <bfields@fieldses.org>
To: Jason Gunthorpe <jgg@ziepe.ca>
Cc: Chuck Lever <chuck.lever@oracle.com>,
Leon Romanovsky <leon@kernel.org>,
Linux NFS Mailing List <linux-nfs@vger.kernel.org>,
linux-rdma@vger.kernel.org
Subject: Re: [PATCH v1 3/3] svcrdma: Fix leak of svc_rdma_recv_ctxt objects
Date: Tue, 14 Apr 2020 12:17:44 -0400 [thread overview]
Message-ID: <20200414161744.GB9796@fieldses.org> (raw)
In-Reply-To: <20200414152016.GE5100@ziepe.ca>
On Tue, Apr 14, 2020 at 12:20:16PM -0300, Jason Gunthorpe wrote:
> On Tue, Apr 14, 2020 at 11:13:03AM -0400, J. Bruce Fields wrote:
> > On Tue, Apr 14, 2020 at 09:19:31AM -0300, Jason Gunthorpe wrote:
> > > On Mon, Apr 13, 2020 at 03:29:07PM -0400, J. Bruce Fields wrote:
> > > > On Thu, Apr 09, 2020 at 02:47:50PM -0300, Jason Gunthorpe wrote:
> > > > > On Thu, Apr 09, 2020 at 10:33:32AM -0400, Chuck Lever wrote:
> > > > > > The commit ID is what automation should key off of. The short
> > > > > > description is only for human consumption.
> > > > >
> > > > > Right, so if the actual commit message isn't included so humans can
> > > > > read it then what was the point of including anything?
> > > >
> > > > Personally as a human reading commits in a terminal window I prefer the
> > > > abbreviated form.
> > >
> > > Frankly, I think they are useless, picking one of yours at random:
> > >
> > > Fixes: 4e48f1cccab3 "NFSD: allow inter server COPY to have... "
> > >
> > > And sadly the '4e48f1cccab3' commit doesn't appear in Linus's tree so
> >
> > Ow, apologies. Looks like I rebased after writing that Fixes tag.
> >
> > I wonder if it's possible to make git warn....
> >
> > Looks like a pre-rebase hook could check the branch being rebased for
> > "Fixes:" lines referencing commits on the rebased branch.
>
> I have some silly stuff to check patches before pushing them and it
> includes checking the fixes lines because they are very often
> wrong, both with wrong commit IDs and wrong subjects!
I'd be interested in seeing it.
> linux-next now automates complaining about them, but perhaps not
> following the standard format defeats that..
It's managed before:
https://lore.kernel.org/r/20190704074048.65556740@canb.auug.org.au
though admittedly I was breaking the rule in a different way. I can't
even be consistently rebellious.
> Use 'git merge-base --is-ancestor fixes_id linus/master' to check
> them.
Oh, yeah, that's better than what I was trying to do, thanks.
--b.
next prev parent reply other threads:[~2020-04-14 16:17 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-07 19:10 [PATCH v1 0/3] NFS/RDMA server fixes for 5.7-rc Chuck Lever
2020-04-07 19:10 ` [PATCH v1 1/3] svcrdma: Fix trace point use-after-free race Chuck Lever
2020-04-07 19:11 ` [PATCH v1 2/3] SUNRPC: Remove naked ->xpo_release_rqst from svc_send() Chuck Lever
2020-04-07 19:11 ` [PATCH v1 3/3] svcrdma: Fix leak of svc_rdma_recv_ctxt objects Chuck Lever
2020-04-08 6:02 ` Leon Romanovsky
2020-04-09 14:33 ` Chuck Lever
2020-04-09 17:47 ` Jason Gunthorpe
2020-04-09 17:59 ` Chuck Lever
2020-04-13 19:29 ` J. Bruce Fields
2020-04-14 12:19 ` Jason Gunthorpe
2020-04-14 15:13 ` J. Bruce Fields
2020-04-14 15:20 ` Jason Gunthorpe
2020-04-14 16:17 ` J. Bruce Fields [this message]
2020-04-14 18:11 ` Leon Romanovsky
2020-04-14 18:15 ` Jason Gunthorpe
2020-04-16 19:05 ` Jason Gunthorpe
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=20200414161744.GB9796@fieldses.org \
--to=bfields@fieldses.org \
--cc=chuck.lever@oracle.com \
--cc=jgg@ziepe.ca \
--cc=leon@kernel.org \
--cc=linux-nfs@vger.kernel.org \
--cc=linux-rdma@vger.kernel.org \
/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).