From: James Hogan <james.hogan@imgtec.com>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: Ralf Baechle <ralf@linux-mips.org>,
Gregory Fong <gregory.0xf0@gmail.com>,
<linux-mips@linux-mips.org>, <stable@vger.kernel.org>
Subject: Re: [PATCH] MIPS: stack protector: Fix per-task canary switch
Date: Mon, 14 Oct 2013 09:40:27 +0100 [thread overview]
Message-ID: <525BADFB.4070601@imgtec.com> (raw)
In-Reply-To: <20131010231617.GI4301@kroah.com>
[-- Attachment #1: Type: text/plain, Size: 709 bytes --]
Hi Greg,
On 11/10/13 00:16, Greg KH wrote:
> On Mon, Oct 07, 2013 at 02:48:59PM +0200, Ralf Baechle wrote:
>> On Mon, Oct 07, 2013 at 12:14:26PM +0100, James Hogan wrote:
>>
>>> Ralf: This is a regression in v3.11, so please consider for v3.12.
>>
>> Applied, will send to Linus with the next pull request.
>
> Which would be in time for 3.12-final, right?
Yes, it's included in v3.12-rc5 as:
8b3c569a3999a8fd5a819f892525ab5520777c92
>> stable folks - please apply to 3.12-stable.
>
> There is no 3.12-stable yet, as 3.12-final isn't out yet.
>
> Confused,
I think Ralf meant v3.11-stable. It's only needed there as the
regression was introduced in v3.11-rc1.
Thanks
James
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
WARNING: multiple messages have this Message-ID (diff)
From: James Hogan <james.hogan@imgtec.com>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: Ralf Baechle <ralf@linux-mips.org>,
Gregory Fong <gregory.0xf0@gmail.com>,
linux-mips@linux-mips.org, stable@vger.kernel.org
Subject: Re: [PATCH] MIPS: stack protector: Fix per-task canary switch
Date: Mon, 14 Oct 2013 09:40:27 +0100 [thread overview]
Message-ID: <525BADFB.4070601@imgtec.com> (raw)
Message-ID: <20131014084027.uDMrHqksxsOncewHje6n482JC9pgEgjgwTWHH0QVQgk@z> (raw)
In-Reply-To: <20131010231617.GI4301@kroah.com>
[-- Attachment #1: Type: text/plain, Size: 709 bytes --]
Hi Greg,
On 11/10/13 00:16, Greg KH wrote:
> On Mon, Oct 07, 2013 at 02:48:59PM +0200, Ralf Baechle wrote:
>> On Mon, Oct 07, 2013 at 12:14:26PM +0100, James Hogan wrote:
>>
>>> Ralf: This is a regression in v3.11, so please consider for v3.12.
>>
>> Applied, will send to Linus with the next pull request.
>
> Which would be in time for 3.12-final, right?
Yes, it's included in v3.12-rc5 as:
8b3c569a3999a8fd5a819f892525ab5520777c92
>> stable folks - please apply to 3.12-stable.
>
> There is no 3.12-stable yet, as 3.12-final isn't out yet.
>
> Confused,
I think Ralf meant v3.11-stable. It's only needed there as the
regression was introduced in v3.11-rc1.
Thanks
James
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2013-10-14 8:41 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-07 11:14 [PATCH] MIPS: stack protector: Fix per-task canary switch James Hogan
2013-10-07 11:14 ` James Hogan
2013-10-07 12:48 ` Ralf Baechle
2013-10-10 23:16 ` Greg KH
2013-10-14 8:40 ` James Hogan [this message]
2013-10-14 8:40 ` James Hogan
2013-10-14 10:27 ` Ralf Baechle
-- strict thread matches above, loose matches on Subject: below --
2013-10-07 11:08 James Hogan
2013-10-07 11:08 ` James Hogan
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=525BADFB.4070601@imgtec.com \
--to=james.hogan@imgtec.com \
--cc=gregkh@linuxfoundation.org \
--cc=gregory.0xf0@gmail.com \
--cc=linux-mips@linux-mips.org \
--cc=ralf@linux-mips.org \
--cc=stable@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