From: Stas Sergeev <stsp@list.ru>
To: Toshi Kani <toshi.kani@hpe.com>,
Linus Torvalds <torvalds@linux-foundation.org>,
Andrew Morton <akpm@linux-foundation.org>,
Toshi Kani <toshi.kani@hp.com>, Ingo Molnar <mingo@kernel.org>
Cc: Andy Lutomirski <luto@amacapital.net>,
Andy Lutomirski <luto@kernel.org>, X86 ML <x86@kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Brian Gerst <brgerst@gmail.com>,
Denys Vlasenko <dvlasenk@redhat.com>,
Borislav Petkov <bp@alien8.de>,
Stas Sergeev <stsp@users.sourceforge.net>
Subject: Re: [PATCH v2 0/4] x86: sigcontext fixes, again
Date: Wed, 28 Oct 2015 12:53:20 +0300 [thread overview]
Message-ID: <56309B10.50706@list.ru> (raw)
In-Reply-To: <1445990693.20657.98.camel@hpe.com>
28.10.2015 03:04, Toshi Kani пишет:
> On Wed, 2015-10-28 at 07:37 +0900, Linus Torvalds wrote:
>> On Tue, Oct 27, 2015 at 11:05 PM, Stas Sergeev <stsp@list.ru> wrote:
>>>
>>> I can't easily post an Oops: under X it doesn't even appear -
>>> machine freezes immediately, and under non-KMS console it is
>>> possible to get one, but difficult to screen-shot (using bare
>>> metal, not VM). Also the Oops was seemingly unrelated.
>>> And if you run "dosemu -s" under non-KMS console, you'll also
>>> reproduce this one:
>>> https://bugzilla.kernel.org/show_bug.cgi?id=97321
>>
>> Hmm. Andrew Morton responded to that initially, but then nothing
>> happened, and now it's been another six months. Andrew?
>>
>> The arch/x86/mm/pat.c error handling does seem to be suspect. This is
>> all code several years old, so none of this is new, and I think Suresh
>> is gone. Adding a few other people with recent sign-offs to that
>> file, in the hope that somebody feels like they own it..
>
> In the case of PFNMAP, the range should always be mapped. So, I wonder why
> follow_phys() failed with the !pte_present() check.
>
> Stas, do you have a test program that can reproduce 97321?
Get dosemu2 from here:
https://github.com/stsp/dosemu2/releases
or from git, or get dosemu1.
Then boot your kernel with "nomodeset=1" to get a text console.
Run
dosemu -s
and you'll get the bug.
You don't even need to mess with FreeDOS or whatever, because
the problem happens on a very start. And since it is WARN_OCNCE,
you'll need to reboot to get it again.
You will probably need to adjust /etc/sudoers because -s means
that dosemu (a wrapper script for dosemu.bin) will try sudo so
that dosemu.bin can grab /dev/mem as root.
If it is too complicated, let me know and I'll try to code up
a reduced test-case (but can't promise to get to that quickly).
Thanks to everyone (esp Linus of course :-) who got involved in
finally supporting dosemu again - it was rather ill for the last
years.
next prev parent reply other threads:[~2015-10-28 9:53 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-26 1:25 [PATCH v2 0/4] x86: sigcontext fixes, again Andy Lutomirski
2015-10-26 1:25 ` [PATCH v2 1/4] x86/signal/64: Add a comment about sigcontext->fs and gs Andy Lutomirski
2015-10-31 15:25 ` Stas Sergeev
2015-12-07 23:23 ` Andy Lutomirski
2015-12-29 12:24 ` Stas Sergeev
2015-12-29 12:31 ` Andy Lutomirski
2015-10-26 1:25 ` [PATCH v2 2/4] x86/signal/64: Fix SS if needed when delivering a 64-bit signal Andy Lutomirski
2015-10-26 1:25 ` [PATCH v2 3/4] x86/signal/64: Re-add support for SS in the 64-bit signal context Andy Lutomirski
2015-10-31 15:18 ` Stas Sergeev
2015-10-26 1:25 ` [PATCH v2 4/4] selftests/x86: Add tests for UC_SIGCONTEXT_SS and UC_STRICT_RESTORE_SS Andy Lutomirski
2015-10-26 11:45 ` [PATCH v2 0/4] x86: sigcontext fixes, again Stas Sergeev
2015-10-27 0:52 ` Andy Lutomirski
2015-10-27 14:05 ` Stas Sergeev
2015-10-27 22:37 ` Linus Torvalds
2015-10-28 0:04 ` Toshi Kani
2015-10-28 9:53 ` Stas Sergeev [this message]
2015-10-28 16:34 ` Toshi Kani
2015-10-28 19:22 ` Toshi Kani
2015-10-28 22:51 ` Toshi Kani
2015-10-31 11:58 ` Stas Sergeev
2015-11-02 17:01 ` Toshi Kani
2015-10-30 23:50 ` Andy Lutomirski
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=56309B10.50706@list.ru \
--to=stsp@list.ru \
--cc=akpm@linux-foundation.org \
--cc=bp@alien8.de \
--cc=brgerst@gmail.com \
--cc=dvlasenk@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=luto@amacapital.net \
--cc=luto@kernel.org \
--cc=mingo@kernel.org \
--cc=stsp@users.sourceforge.net \
--cc=torvalds@linux-foundation.org \
--cc=toshi.kani@hp.com \
--cc=toshi.kani@hpe.com \
--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 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.