linux-kernel - Re: [PATCH] Fix stack corruption on some architectures

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: <1376951983.5082.18.camel@chimera>
Date:	Mon, 19 Aug 2013 15:39:43 -0700
From:	Daniel Gimpelevich <daniel@...pelevich.san-francisco.ca.us>
To:	Sergei Shtylyov <sergei.shtylyov@...entembedded.com>
Cc:	Jan Dumon <j.dumon@...ion.com>,
	Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
	linux-usb@...r.kernel.org, netdev@...r.kernel.org,
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH] Fix stack corruption on some architectures

On Tue, 2013-08-20 at 02:31 +0400, Sergei Shtylyov wrote: 
> Hello.
> 
> On 08/20/2013 12:37 AM, Daniel Gimpelevich wrote:
> 
> > There is no need to get an interface specification if we know it's the
> > wrong one; trivial change.
> 
>     Is it related to stack corruption? If not, it's asking to be in a separate 
> patch.

Perhaps, but I'll leave that up to the maintainer(s). You should be
credited as co-author of the patch.

--
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/