From: ddu <dengke.du@windriver.com>
To: <linux-rt-users@vger.kernel.org>
Subject: rt kernel break printf command's parent process
Date: Mon, 27 May 2019 17:47:04 +0800 [thread overview]
Message-ID: <205dd879-fedc-2edf-92b3-0bd8a3ee1870@windriver.com> (raw)
Hi all
I use yocto rt-kernel which rebase on rt kernel:
http://git.yoctoproject.org/cgit/cgit.cgi/linux-yocto/log/?h=v5.0/standard/preempt-rt/intel-x86
yocto branch: master
run command:
printf "%0.0f\n" 123.4567
error:
[ OK ] Stopped Serial Getty on ttyS0.
[ OK ] Started Serial Getty on ttyS0.
the system loged out, and let login again.
I using bisect to find which commit break the it:
---------------------------------------------------------------------------
commit 6115b04921fc2b8a6b9f7de6d35a0202204a36ba
Author: Rik van Riel <riel@surriel.com>
Date: Sun Sep 9 18:30:50 2018 +0200
x86/fpu: Always store the registers in copy_fpstate_to_sigframe()
copy_fpstate_to_sigframe() stores the registers directly to user space.
This is okay because the FPU register are valid and saving it directly
avoids saving it into kernel memory and making a copy.
However<E2><80><A6> We can't keep doing this if we are going to
restore the FPU
registers on the return to userland. It is possible that the FPU
registers will be invalidated in the middle of the save operation and
this should be done with disabled preemption / BH.
Save the FPU registers to task's FPU struct and copy them to the user
memory later on.
This code is extracted from an earlier version of the patchset while
there still was lazy-FPU on x86.
Signed-off-by: Rik van Riel <riel@surriel.com>
Signed-off-by: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
---------------------------------------------------------------------------
When I want to revert it, I found it's a serial patches, so if I revert
it, I need to revert a serial patches.
So can anyone help me to trace where break the return from printf and
break the parent process?
next reply other threads:[~2019-05-27 9:47 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-27 9:47 ddu [this message]
2019-05-28 14:33 ` rt kernel break printf command's parent process Sebastian Andrzej Siewior
2019-05-28 16:04 ` Sebastian Andrzej Siewior
2019-05-30 2:19 ` ddu
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=205dd879-fedc-2edf-92b3-0bd8a3ee1870@windriver.com \
--to=dengke.du@windriver.com \
--cc=linux-rt-users@vger.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.