lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <5212FCA8.9040204@synopsys.com>
Date:	Tue, 20 Aug 2013 10:50:40 +0530
From:	Vineet Gupta <Vineet.Gupta1@...opsys.com>
To:	greg Kroah-Hartman <gregkh@...uxfoundation.org>
CC:	"stable@...r.kernel.org" <stable@...r.kernel.org>,
	"noamc@...hip.com" <noamc@...hip.com>,
	Anton Kolesov <Anton.Kolesov@...opsys.com>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH 1/2] ARC: gdbserver breakage in Big-Endian configuration
 #1

Hi Greg,

On 08/19/2013 08:27 PM, greg Kroah-Hartman wrote:
> On Mon, Aug 19, 2013 at 09:08:49AM +0000, Vineet Gupta wrote:
>> Hi Greg,
>>
>> I'd posted these patches for stable backport. Do I need to do anything more to get them included.
>>
>> https://patchwork.kernel.org/patch/2841153/  [1/2] ARC: gdbserver breakage in Big-Endian configuration #1<https://patchwork.kernel.org/patch/2841153/>]
>> https://patchwork.kernel.org/patch/2841158/  [2/2] ARC: gdbserver breakage in Big-Endian configuration #2<https://patchwork.kernel.org/patch/2841158/>
> 
> I ignored them as I thought you were submitting them for upstream
> inclusion.  If they are already in Linus's tree, then take a look at the
> file, Documentation/stable_kernel_rules.txt for how to send a patch for
> inclusion into a stable release (hint, I need to know the git commit id
> that the patch has in Linus's tree, which I didn't see anywhere here.)


I'm sure I mentioned the commit-id in the patch. Hint, please look at annotation
within --->8--- blocks in changelogs.

The caveat however is we can't apply those exact commits as it is as that warrants
more changes to be pulled in. However I'm going by the last stable kernel rule "It
or an equivalent fix must already exist in Linus' tree (upstream)."

Anyhow, since both these patches are extracted from same commit, I'll respin a
single patch (with a small addition - again part of the same commit) and send it
over. OK !

Thx,
-Vineet
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ