On Wed, 2013-09-11 at 15:26 -0400, David Miller wrote: > From: Luis Henriques <luis.henriques@xxxxxxxxxxxxx> > Date: Wed, 11 Sep 2013 11:57:17 +0100 > > > David Miller <davem@xxxxxxxxxxxxx> writes: > > > >> Please apply the following patches to 3.0.x, 3.2.x, 3.4.x, and > >> 3.10.x -stable, respectively. > >> > >> Thanks! > >> > >> > >> > >> > > > > I was looking at the backport for commit > > > > 85dfb745ee40232876663ae206cba35f24ab2a40 af_key: initialize satype in key_notify_policy_flush() > > > > and I believe there's something wrong with it. It patches function > > key_notify_sa_flush() instead of key_notify_policy_flush(). Is this > > correct or a mistake? > > > > otoh, all the affected kernels seem to have already a (correct?) > > backport of this commit. > > It's possible I messed this one up, thanks for catching it I'll take > a closer look. My script shows these: $ git check-in-stable 85dfb745ee40232876663ae206cba35f24ab2a40 3.0: e00f3fd af_key: initialize satype in key_notify_policy_flush() 3.2: 54811a1 af_key: initialize satype in key_notify_policy_flush() 3.4: 1a5abb4 af_key: initialize satype in key_notify_policy_flush() This fix was requested in: http://thread.gmane.org/gmane.linux.kernel.stable/62076 and it looks like Greg and I didn't recognise it as being in your domain, so we applied directly. Ben. -- Ben Hutchings If more than one person is responsible for a bug, no one is at fault.
Attachment:
signature.asc
Description: This is a digitally signed message part