netdev - Re: [PATCH v2] vmalloc: Fix issues with flush flag

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]

Date:   Mon, 20 May 2019 20:33:20 -0400 (EDT)
From:   David Miller <davem@...emloft.net>
To:     rick.p.edgecombe@...el.com
Cc:     linux-kernel@...r.kernel.org, peterz@...radead.org,
        linux-mm@...ck.org, mroos@...ux.ee, mingo@...hat.com,
        namit@...are.com, luto@...nel.org, bp@...en8.de,
        netdev@...r.kernel.org, dave.hansen@...el.com,
        sparclinux@...r.kernel.org
Subject: Re: [PATCH v2] vmalloc: Fix issues with flush flag

From: "Edgecombe, Rick P" <rick.p.edgecombe@...el.com>
Date: Tue, 21 May 2019 00:20:13 +0000

> This behavior shouldn't happen until modules or BPF are being freed.

Then that would rule out my theory.

The only thing left is whether the permissions are actually set
properly.  If they aren't we'll take an exception when the BPF program
is run and I'm not %100 sure that kernel execute permission violations
are totally handled cleanly.