From: Mathieu Desnoyers <mathieu.desnoyers@efficios.com>
To: Mingyi Liu <mingyiliu@gatech.edu>
Cc: linux-kernel <linux-kernel@vger.kernel.org>,
Peter Zijlstra <peterz@infradead.org>,
paulmck <paulmck@kernel.org>, Boqun Feng <boqun.feng@gmail.com>
Subject: Re: about seg fault inside rseq critical section
Date: Wed, 7 Apr 2021 09:25:01 -0400 (EDT) [thread overview]
Message-ID: <723248518.60240.1617801901472.JavaMail.zimbra@efficios.com> (raw)
In-Reply-To: <MN2PR07MB80147F72667BBA151586486ED1769@MN2PR07MB8014.namprd07.prod.outlook.com>
(re-sent in plain-text for lkml)
----- On Apr 6, 2021, at 6:24 PM, Mingyi Liu mingyiliu@gatech.edu wrote:
> Hi Mathieu,
> I notice that the program will be terminated with segmentation fault when it is
> even seg faulted inside the rseq critical section. In Linux kernel rseq.c, I
> haven't found comment or code regarding this. Could you share any references on
> why it doesn't execute user defined abort handler but uses the OS handler
> instead?
> Thanks in advance!
Hi Mingyi,
Please let me add the other rseq maintainers and LKML in CC. I'm a bit stretched on time
here, so maybe they will have time to answer before I do.
Meanwhile, if you could provide details about your architecture, kernel .config, and a
small reproducer program, it would help bootstrapping the discussion.
Thanks,
Mathieu
> Best,
> Mingyi
--
Mathieu Desnoyers
EfficiOS Inc.
http://www.efficios.com
next parent reply other threads:[~2021-04-07 13:25 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <MN2PR07MB80147F72667BBA151586486ED1769@MN2PR07MB8014.namprd07.prod.outlook.com>
2021-04-07 13:25 ` Mathieu Desnoyers [this message]
[not found] ` <MN2PR07MB8014361586F3E8DAF347A8C6D1729@MN2PR07MB8014.namprd07.prod.outlook.com>
2021-04-11 0:30 ` about seg fault inside rseq critical section Mathieu Desnoyers
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=723248518.60240.1617801901472.JavaMail.zimbra@efficios.com \
--to=mathieu.desnoyers@efficios.com \
--cc=boqun.feng@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingyiliu@gatech.edu \
--cc=paulmck@kernel.org \
--cc=peterz@infradead.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