Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18;
Date:   Fri, 4 Jun 2021 16:54:15 +0200
From:   Borislav Petkov <bp@alien8.de>
To:     "Eric W. Biederman" <ebiederm@xmission.com>, mtk@man7.org
Cc:     Jiashuo Liang <liangjs@pku.edu.cn>,
        Dave Hansen <dave.hansen@linux.intel.com>,
        Andy Lutomirski <luto@kernel.org>,
        Peter Zijlstra <peterz@infradead.org>,
        Thomas Gleixner <tglx@linutronix.de>,
        Ingo Molnar <mingo@redhat.com>, x86@kernel.org,
        "H. Peter Anvin" <hpa@zytor.com>, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] signal/x86: Don't send SIGSEGV twice on SEGV_PKUERR
Message-ID: <YLo+l4KyKNPxupM2@zn.tnic>
References: <20210601085203.40214-1-liangjs@pku.edu.cn>
 <YLkhV+lSqXlcfUc5@zn.tnic>
 <87lf7qocsd.fsf@disp2133>
 <YLolc7z64h9yHNao@zn.tnic>
 <878s3plmxj.fsf@disp2133>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
In-Reply-To: <878s3plmxj.fsf@disp2133>
Precedence: bulk

On Fri, Jun 04, 2021 at 09:33:12AM -0500, Eric W. Biederman wrote:
> At some point I just figured someone needs to take the time to
> understand the linux signal handling and get as many bugs out as we
> can.  It may not be flashy but it is one of those core things
> that everything is built on so we need code that works.

Oh yeah, good idea. Signals and their handling make most people cringe.

Also, selftests. I wonder if it would be a good idea to make it a
kernelnewbies project for people to do short programs, each exercising
an API from the Linux manpages.

Or maybe even get Michael (CCed) to donate some of the examples from his
book:

https://man7.org/tlpi/code/online/all_files_by_chapter.html

in this case, chapters 20-22, as selftests for the kernel. Or maybe even
all examples. :-)

Just an idea anyway.

Thx.

-- 
Regards/Gruss,
    Boris.

https://people.kernel.org/tglx/notes-about-netiquette