From: Pavel Machek <pavel@ucw.cz>
To: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
Cc: kernel list <linux-kernel@vger.kernel.org>,
tglx@linutronix.de, mingo@redhat.com, bp@alien8.de,
hpa@zytor.com, x86@kernel.org
Subject: Re: 5.2-rc0.8: emacs segfaults?! x220, with 32-bit userland
Date: Tue, 21 May 2019 01:13:42 +0200 [thread overview]
Message-ID: <20190520231342.GA20835@amd> (raw)
In-Reply-To: <20190520160636.z6fpjiidc2d5ko5g@linutronix.de>
[-- Attachment #1: Type: text/plain, Size: 748 bytes --]
Hi!
> > emacs segfaults... when I attempt to exit it. And that did not use to
> > be the case. Nothing suspect in the dmesg. Rest of the machine seems
> > to work ok.
> …
> > Ideas welcome...
>
> I assume that this happens with -rc1, too. Could you please check if
> emacs still segfaults with commit
>
> d9c9ce34ed5c8 ("x86/fpu: Fault-in user stack if copy_fpstate_to_sigframe() fails")
>
> and commit
>
> 89833fab15d60 ("x86/fpu: Fix __user annotations")
>
> ?
I don't have reproducible test case :-(. I had two or three failures
so far.
Best regards,
Pavel
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 181 bytes --]
next prev parent reply other threads:[~2019-05-20 23:13 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-19 22:17 5.2-rc0.8: emacs segfaults?! x220, with 32-bit userland Pavel Machek
2019-05-20 16:06 ` Sebastian Andrzej Siewior
2019-05-20 23:13 ` Pavel Machek [this message]
2019-05-21 7:32 ` Sebastian Andrzej Siewior
2019-05-22 18:33 ` Pavel Machek
2019-05-23 8:37 ` 5.1.0-next-20190520 -- emacs segfaults on 32-bit machine " Pavel Machek
2019-05-23 8:57 ` Pavel Machek
2019-05-23 14:50 ` Sebastian Andrzej Siewior
2019-05-27 13:03 ` Pavel Machek
2019-05-27 13:08 ` Sebastian Andrzej Siewior
2019-05-27 21:46 ` Pavel Machek
2019-06-01 21:30 ` Pavel Machek
2019-05-27 13:03 ` Pavel Machek
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=20190520231342.GA20835@amd \
--to=pavel@ucw.cz \
--cc=bigeasy@linutronix.de \
--cc=bp@alien8.de \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--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 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.