Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20;
MIME-Version: 1.0
References: <20220606203802.158958-1-brgerst@gmail.com> <53296bc3-d220-dfe5-514b-bba2496ef4b3@kernel.org>
In-Reply-To: <53296bc3-d220-dfe5-514b-bba2496ef4b3@kernel.org>
From:   Brian Gerst <brgerst@gmail.com>
Date:   Wed, 29 Jun 2022 11:21:17 -0400
Message-ID: <CAMzpN2iBk4bfFWyxrMtFanxxNAM9MYNXPZ3oQSmyBpQjuNP_Ug@mail.gmail.com>
Subject: Re: [PATCH 0/8] x86 signal code cleanups
To:     Andy Lutomirski <luto@kernel.org>
Cc:     Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
        "the arch/x86 maintainers" <x86@kernel.org>,
        Thomas Gleixner <tglx@linutronix.de>,
        Borislav Petkov <bp@alien8.de>,
        "H . Peter Anvin" <hpa@zytor.com>,
        Peter Zijlstra <peterz@infradead.org>,
        "Eric W . Biederman" <ebiederm@xmission.com>
Content-Type: text/plain; charset="UTF-8"
Precedence: bulk

On Tue, Jun 28, 2022 at 7:23 PM Andy Lutomirski <luto@kernel.org> wrote:
>
> On 6/6/22 13:37, Brian Gerst wrote:
> > The 32-bit signal code has significant differences from 64-bit, and
> > those are duplicated for native and compat modes.  This patch series
> > merges the 32-bit code into one file, and does some general cleanups
> > in the x86 signal code.  There should be no functional changes.
> >
>
> This looks generally sane.  What kind of testing have you done?

I ran all of the self tests, did a parallel kernel build, and general
usage like web browsing.  Do you have any suggestions for other tests?

--
Brian Gerst