| 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
| ||
|
Message-ID: <8ca9f320-8e05-4232-9d78-d2326e4f6720@intel.com> Date: Mon, 21 Jul 2025 09:45:06 -0700 From: Dave Hansen <dave.hansen@...el.com> To: Jarkko Sakkinen <jarkko@...nel.org>, Elena Reshetova <elena.reshetova@...el.com> Cc: seanjc@...gle.com, kai.huang@...el.com, mingo@...nel.org, linux-sgx@...r.kernel.org, linux-kernel@...r.kernel.org, x86@...nel.org, asit.k.mallick@...el.com, vincent.r.scarlata@...el.com, chongc@...gle.com, erdemaktas@...gle.com, vannapurve@...gle.com, bondarn@...gle.com, scott.raynor@...el.com Subject: Re: [PATCH v8 5/5] x86/sgx: Enable automatic SVN updates for SGX enclaves On 7/19/25 04:22, Jarkko Sakkinen wrote: > On Tue, Jul 15, 2025 at 03:40:22PM +0300, Elena Reshetova wrote: >> -static int __maybe_unused sgx_update_svn(void) >> +static int sgx_update_svn(void) > I'd combine 4/5 and 5/5 because of this. Makes them so much easier to > backtrack changes later on if this type of stuff is avoided when > possible. I'm not really sure what "backtracking changes" is, but I disagree on this one. Breaking up patches is about reducing the mental load to review things. Generally, the smaller the patch, the smaller the mental load. That breaks down when, for instance, a helper has a complicated argument handling or return codes. But, in this case, we have a function that takes no arguments and returns standard -ERROR codes. It's fine to break it out like this. No reason to do more patch gymnastics at this point to squash it.
Powered by blists - more mailing lists