netdev - Re: [PATCH net 2/2] s390/bpf: fix bpf frame pointer setup

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]

Message-Id: <20150603.193217.279547964953271748.davem@davemloft.net>
Date:	Wed, 03 Jun 2015 19:32:17 -0700 (PDT)
From:	David Miller <davem@...emloft.net>
To:	ast@...mgrid.com
Cc:	holzheu@...ux.vnet.ibm.com, schwidefsky@...ibm.com,
	heiko.carstens@...ibm.com, daniel@...earbox.net,
	netdev@...r.kernel.org
Subject: Re: [PATCH net 2/2] s390/bpf: fix bpf frame pointer setup

From: Alexei Starovoitov <ast@...mgrid.com>
Date: Mon,  1 Jun 2015 22:48:35 -0700

> From: Michael Holzheu <holzheu@...ux.vnet.ibm.com>
> 
> Currently the bpf frame pointer is set to the old r15. This is
> wrong because of packed stack. Fix this and adjust the frame pointer
> to respect packed stack. This now generates a prolog like the following:
> 
>  3ff8001c3fa: eb67f0480024   stmg    %r6,%r7,72(%r15)
>  3ff8001c400: ebcff0780024   stmg    %r12,%r15,120(%r15)
>  3ff8001c406: b904001f       lgr     %r1,%r15      <- load backchain
>  3ff8001c40a: 41d0f048       la      %r13,72(%r15) <- load adjusted bfp
>  3ff8001c40e: a7fbfd98       aghi    %r15,-616
>  3ff8001c412: e310f0980024   stg     %r1,152(%r15) <- save backchain
> 
> Fixes: 054623105728 ("s390/bpf: Add s390x eBPF JIT compiler backend")
> Signed-off-by: Michael Holzheu <holzheu@...ux.vnet.ibm.com>
> Acked-by: Heiko Carstens <heiko.carstens@...ibm.com>
> Signed-off-by: Alexei Starovoitov <ast@...mgrid.com>

Applied.
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html