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: <44103bd1-47e9-0d98-770f-010a1077346c@cs.kuleuven.be>
Date:   Fri, 18 Aug 2023 18:09:19 -0700
From:   Jo Van Bulck <jo.vanbulck@...kuleuven.be>
To:     "Huang, Kai" <kai.huang@...el.com>,
        "linux-sgx@...r.kernel.org" <linux-sgx@...r.kernel.org>,
        "jarkko@...nel.org" <jarkko@...nel.org>,
        "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Cc:     "dave.hansen@...ux.intel.com" <dave.hansen@...ux.intel.com>
Subject: Re: [PATCH 6/8] selftests/sgx: Ensure expected enclave data buffer
 size and placement

On 18.08.23 06:10, Huang, Kai wrote:
> Firstly, these two problems are independent. Could you split this into two
> patches?  One to preserve the entire buffer, the other to always place the
> buffer at the beginning.

Makes sense, doing this for the next revision.

> Secondly, as replied to v1, I think we can use "used" gcc attribute to always
> preserve the buffer?

Thanks for the suggestion. Yes, I was not aware of this attribute, but 
it is indeed exactly what we need in this case. Applying this in the 
next revision.

Best,
Jo

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ