linux-kernel - Re: [PATCH net-next 04/24] rxrpc: Avoid using stack memory in SG lists in rxkad

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] [day] [month] [year] [list]

Date:	Wed, 06 Jul 2016 16:03:08 +0100
From:	David Howells <dhowells@...hat.com>
To:	Andy Lutomirski <luto@...capital.net>
Cc:	dhowells@...hat.com, "David S. Miller" <davem@...emloft.net>,
	Herbert Xu <herbert@...dor.apana.org.au>,
	Network Development <netdev@...r.kernel.org>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	Andy Lutomirski <luto@...nel.org>,
	linux-afs@...ts.infradead.org
Subject: Re: [PATCH net-next 04/24] rxrpc: Avoid using stack memory in SG lists in rxkad

Andy Lutomirski <luto@...capital.net> wrote:

> > From: Herbert Xu <herbert@...dor.apana.org.au>
> >
> > rxkad uses stack memory in SG lists which would not work if stacks were
> > allocated from vmalloc memory.  In fact, in most cases this isn't even
> > necessary as the stack memory ends up getting copied over to kmalloc
> > memory.
> 
> This version no longer applies to Linus' tree, so I'm dropping it from
> my series.

This version of your rxrpc patch?  There haven't been any conflicting upstream
changes for a month.  Do you object to me carrying my version of the patch
since it fits in with the changes I've been making?

David