stable.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
* stable-request: bpf 2017-12-12
@ 2017-12-13 14:38 Daniel Borkmann
  2017-12-14 17:47 ` Greg KH
  0 siblings, 1 reply; 3+ messages in thread
From: Daniel Borkmann @ 2017-12-13 14:38 UTC (permalink / raw)
  To: gregkh; +Cc: daniel, ast, stable

Hi Greg,

It would be great if you could cherry-pick the following BPF related
commit into stable trees:

  c131187db2d3 ("bpf: fix branch pruning logic")  -  up to 4.9

  Instructions for 4.14:

    There's a minor conflict in verifier.c, just take the
    'env->insn_aux_data[insn_idx].seen = true;' part from
    the patch.

  Instructions for 4.9:

    Needs 8041902dae52 ("bpf: adjust insn_aux_data when patching
    insns") as prerequisite. Same minor conflict in verifier.c
    as with 4.14 described above. The minor one in bpf_verifier.h
    for struct bpf_insn_aux_data should be resolved by having
    'ptr_type' and 'seen' as final members of the struct.

Thanks a lot!

^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: stable-request: bpf 2017-12-12
  2017-12-13 14:38 stable-request: bpf 2017-12-12 Daniel Borkmann
@ 2017-12-14 17:47 ` Greg KH
  2017-12-14 19:47   ` Daniel Borkmann
  0 siblings, 1 reply; 3+ messages in thread
From: Greg KH @ 2017-12-14 17:47 UTC (permalink / raw)
  To: Daniel Borkmann; +Cc: ast, stable

On Wed, Dec 13, 2017 at 03:38:01PM +0100, Daniel Borkmann wrote:
> Hi Greg,
> 
> It would be great if you could cherry-pick the following BPF related
> commit into stable trees:
> 
>   c131187db2d3 ("bpf: fix branch pruning logic")  -  up to 4.9
> 
>   Instructions for 4.14:
> 
>     There's a minor conflict in verifier.c, just take the
>     'env->insn_aux_data[insn_idx].seen = true;' part from
>     the patch.
> 
>   Instructions for 4.9:
> 
>     Needs 8041902dae52 ("bpf: adjust insn_aux_data when patching
>     insns") as prerequisite. Same minor conflict in verifier.c
>     as with 4.14 described above. The minor one in bpf_verifier.h
>     for struct bpf_insn_aux_data should be resolved by having
>     'ptr_type' and 'seen' as final members of the struct.

Can you just provide patches that you backported and verified to be
correct?  That ensures I don't mess it up :)

thanks,

greg k-h

^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: stable-request: bpf 2017-12-12
  2017-12-14 17:47 ` Greg KH
@ 2017-12-14 19:47   ` Daniel Borkmann
  0 siblings, 0 replies; 3+ messages in thread
From: Daniel Borkmann @ 2017-12-14 19:47 UTC (permalink / raw)
  To: Greg KH; +Cc: ast, stable

On 12/14/2017 06:47 PM, Greg KH wrote:
> On Wed, Dec 13, 2017 at 03:38:01PM +0100, Daniel Borkmann wrote:
>> Hi Greg,
>>
>> It would be great if you could cherry-pick the following BPF related
>> commit into stable trees:
>>
>>   c131187db2d3 ("bpf: fix branch pruning logic")  -  up to 4.9
>>
>>   Instructions for 4.14:
>>
>>     There's a minor conflict in verifier.c, just take the
>>     'env->insn_aux_data[insn_idx].seen = true;' part from
>>     the patch.
>>
>>   Instructions for 4.9:
>>
>>     Needs 8041902dae52 ("bpf: adjust insn_aux_data when patching
>>     insns") as prerequisite. Same minor conflict in verifier.c
>>     as with 4.14 described above. The minor one in bpf_verifier.h
>>     for struct bpf_insn_aux_data should be resolved by having
>>     'ptr_type' and 'seen' as final members of the struct.
> 
> Can you just provide patches that you backported and verified to be
> correct?  That ensures I don't mess it up :)

Sure that's fine. I'll send them tomorrow.

Thanks,
Daniel

^ permalink raw reply	[flat|nested] 3+ messages in thread

end of thread, other threads:[~2017-12-14 19:47 UTC | newest]

Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2017-12-13 14:38 stable-request: bpf 2017-12-12 Daniel Borkmann
2017-12-14 17:47 ` Greg KH
2017-12-14 19:47   ` Daniel Borkmann

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).