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: <5e0f1ae7-3a69-0d1c-3f33-ddb44ed8b6c5@redhat.com>
Date:   Tue, 1 Aug 2017 09:10:05 +0530
From:   Pratyush Anand <panand@...hat.com>
To:     Yury Norov <ynorov@...iumnetworks.com>,
        Catalin Marinas <catalin.marinas@....com>,
        linux-arm-kernel@...ts.infradead.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH RFC] arm64: introduce mm_context_t flags



On Monday 31 July 2017 08:18 PM, Yury Norov wrote:
>   - If we start using TIF flags here, we cannot easily add new mm_context
>     specific bits because they may mess with TIF ones.

This one seems convincing argument. ATM do you have any mm_context flag which 
would you like to incorporate?

> 
> I think that this is not what was intended when you added new field in
> mm_context_t.
> 
> In this patch the MMCF_AARCH32 flag is introduced, where MMCF prefix stands for
> mm_context_t flags. And the new flag is used for uprobes code instead of TIF_32BIT.

-- 
Regards
Pratyush

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ