From: <shai@ftcon.com>
To: <linux-kernel@vger.kernel.org>
Subject: lowlatency patch question
Date: Sat, 10 Jan 2004 19:31:47 -0800 [thread overview]
Message-ID: <200401110331.BBB99015@ms6.verisignmail.com> (raw)
Hi,
I think the following is a bug that can affect kernels patched with
lowlatency, such as Audio
and RedHat AS2.1.
lowlatency patch added conditional_schedule() to be called from
close_files(
) at kernel/exit.c, which seems to raise a problem if the
process had LDT entries.
If it had LDT, at the stage of close_files(
) the tsk->mm already zeroed
(__exit_mm(
), which comes before __exit_files(
) in do_exit(
)). If
conditional_schedule() at close_files(
) will succeed, switching back into
this process (that now have zeroed tsk->mm) will fail since the kernel will
not use the right LDT (since tsk->mm was zeroed, so switch_mm(
) will not be
called to load the LDT at schedule()).
Switching back to a process that had a register that used the LDT will fail
since the register probably points to non-valid LDT entry (since we are
using the wrong LDT), which will lead to a segmentation fault.
--Shai
next reply other threads:[~2004-01-11 3:31 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-11 3:31 shai [this message]
2004-01-11 9:48 ` lowlatency patch question Arjan van de Ven
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=200401110331.BBB99015@ms6.verisignmail.com \
--to=shai@ftcon.com \
--cc=linux-kernel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox