[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20190614103135.lo4u25brtbrnalnm@azazel.net>
Date: Fri, 14 Jun 2019 11:31:35 +0100
From: Jeremy Sowden <jeremy@...zel.net>
To: Steffen Klassert <steffen.klassert@...unet.com>
Cc: herbert@...dor.apana.org.au, davem@...emloft.net,
netdev@...r.kernel.org
Subject: Re: [PATCH] af_key: Fix memory leak in key_notify_policy.
On 2019-06-14, at 12:17:08 +0200, Steffen Klassert wrote:
> On Fri, Jun 14, 2019 at 11:13:38AM +0100, Jeremy Sowden wrote:
> > That reminds me. Stephen Rothwell reported a problem with the
> > "Fixes:" tag:
> >
> > On 2019-05-29, at 07:48:12 +1000, Stephen Rothwell wrote:
> > > In commit
> > >
> > > 7c80eb1c7e2b ("af_key: fix leaks in key_pol_get_resp and dump_sp.")
> > >
> > > Fixes tag
> > >
> > > Fixes: 55569ce256ce ("Fix conversion between IPSEC_MODE_xxx and XFRM_MODE_xxx.")
> > >
> > > has these problem(s):
> > >
> > > - Subject does not match target commit subject
> > > Just use
> > > git log -1 --format='Fixes: %h ("%s")'
> >
> > What's the procedure for fixing this sort of thing? Do you need me
> > to do anything?
>
> No, that patch is already commited. We can't change the commit message
> anymore. Just keep it in mind for next time.
Will do. I've already made a note of that git-log invocation. Useful
to know.
J.
Download attachment "signature.asc" of type "application/pgp-signature" (834 bytes)
Powered by blists - more mailing lists