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
Date: Fri, 4 Jun 2021 16:54:15 +0200 [thread overview]
Message-ID: <YLo+l4KyKNPxupM2@zn.tnic> (raw)
In-Reply-To: <878s3plmxj.fsf@disp2133>
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
next prev parent reply other threads:[~2021-06-04 14:54 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-01 8:52 [PATCH] signal/x86: Don't send SIGSEGV twice on SEGV_PKUERR Jiashuo Liang
2021-06-02 18:42 ` Eric W. Biederman
2021-06-02 19:02 ` Borislav Petkov
2021-06-03 18:37 ` Borislav Petkov
2021-06-03 21:31 ` Eric W. Biederman
2021-06-04 13:06 ` Borislav Petkov
2021-06-04 14:33 ` Eric W. Biederman
2021-06-04 14:54 ` Borislav Petkov [this message]
2021-06-04 13:26 ` [tip: x86/urgent] x86/fault: " tip-bot2 for Jiashuo Liang
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=YLo+l4KyKNPxupM2@zn.tnic \
--to=bp@alien8.de \
--cc=dave.hansen@linux.intel.com \
--cc=ebiederm@xmission.com \
--cc=hpa@zytor.com \
--cc=liangjs@pku.edu.cn \
--cc=linux-kernel@vger.kernel.org \
--cc=luto@kernel.org \
--cc=mingo@redhat.com \
--cc=mtk@man7.org \
--cc=peterz@infradead.org \
--cc=tglx@linutronix.de \
--cc=x86@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).