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: <20200214.095303.341559462549043464.davem@davemloft.net>
Date:   Fri, 14 Feb 2020 09:53:03 -0800 (PST)
From:   David Miller <davem@...emloft.net>
To:     tglx@...utronix.de
Cc:     linux-kernel@...r.kernel.org, bpf@...r.kernel.org,
        netdev@...r.kernel.org, ast@...nel.org, daniel@...earbox.net,
        bigeasy@...utronix.de, peterz@...radead.org, williams@...hat.com,
        rostedt@...dmis.org, juri.lelli@...hat.com, mingo@...nel.org
Subject: Re: [RFC patch 00/19] bpf: Make BPF and PREEMPT_RT co-exist

From: Thomas Gleixner <tglx@...utronix.de>
Date: Fri, 14 Feb 2020 14:39:17 +0100

> This is a follow up to the initial patch series which David posted a
> while ago:
> 
>  https://lore.kernel.org/bpf/20191207.160357.828344895192682546.davem@davemloft.net/
> 
> which was (while non-functional on RT) a good starting point for further
> investigations.

This looks really good after a cursory review, thanks for doing this week.

I was personally unaware of the pre-allocation rules for MAPs used by
tracing et al.  And that definitely shapes how this should be handled.

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ