linux-kernel - Re: [PATCH] x86/sgx: Avoid returning NULL in __sgx_alloc_epc

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: <YFTB0HD/4Hc0KvT3@kernel.org>
Date:   Fri, 19 Mar 2021 17:22:56 +0200
From:   Jarkko Sakkinen <jarkko@...nel.org>
To:     Borislav Petkov <bp@...en8.de>
Cc:     Kai Huang <kai.huang@...el.com>, x86@...nel.org,
        linux-sgx@...r.kernel.org, dave.hansen@...ux.intel.com,
        dave.hansen@...el.com, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] x86/sgx: Avoid returning NULL in __sgx_alloc_epc_page()

On Fri, Mar 19, 2021 at 03:59:31PM +0100, Borislav Petkov wrote:
> On Fri, Mar 19, 2021 at 04:50:33PM +0200, Jarkko Sakkinen wrote:
> > > > I was on the verge whether to merge that into the original patch since
> > > > it is the top patch on the branch or create a new one but opted for
> > > > former because this way it won't break bisection and people won't have
> > > > to pay attention whether there's a fix patch to the NUMA patch too, in
> > > > case they wanna backport and whatnot.
> 
> ...
> 
> > I understood Boris' comment that the fixes would not be squashed.
> 
> Please read it again and let me know what about it is not clear. It is
> at the beginning of this mail.

I did misread it for the first time.

So let's sanity: you *are* going to squash the patches together because
that way it's factors easier to backport the whole thing?

Is this the correct understanding?

Fair point, I can cope with that.

> -- 
> Regards/Gruss,
>     Boris.
> 
> https://people.kernel.org/tglx/notes-about-netiquette
> 

/Jarkko