[lkml]   [2022]   [Jun]   [29]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
    SubjectRe: [PATCH] remove CONFIG_ANDROID
    On Wed, Jun 29, 2022 at 06:15:27PM +0200, Christoph Hellwig wrote:
    > On Wed, Jun 29, 2022 at 06:13:05PM +0200, Jason A. Donenfeld wrote:
    > > Good! It sounds like you're starting to develop opinions on the matter.
    > No, I provide facts.


    > Look at both the definition of the symbol, and
    > various distribution kernel that enabled it and think hard if they run
    > on "Android" hardware. Not just primarily, but at all.

    There are two failure modes:

    1) Key clearing code is skipped when it shouldn't be.
    2) Key clearing code is run when it shouldn't be.

    You've identified (well, Alex in the other thread I think?) a case of
    (1). I was sort of thinking the fix to that would be that distros
    shouldn't enable that option, but it doesn't really matter to me.

    However, what I'm pointing out is the potential for (2). A (2)-style
    regression means that WireGuard basically doesn't work, because, for
    example, qcacld's packet-triggered wakeups tend to be too short to
    renegotiate a handshake.

    Anyway, instead of the slow drip of "facts" and ≤three sentence emails,
    can you just write up a paragraph that indicates this is safe to do (for
    both (1) and (2)) in your v+1?

    I don't really want to argue about it, because I don't have anything to
    argue about. Your change is probably fine. I'd just like it to be
    spelled out why this is safe to do from somebody who has looked into it.
    I have not looked into it, but it sounds like you have or are in the
    process of doing so. Just write down what you find, please.


     \ /
      Last update: 2022-06-29 18:27    [W:12.433 / U:0.100 seconds]
    ©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site