linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Fiona Ebner <f.ebner@proxmox.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: "Eric W. Biederman" <ebiederm@xmission.com>,
	Oleg Nesterov <oleg@redhat.com>,
	akpm@linux-foundation.org,
	Thomas Lamprecht <t.lamprecht@proxmox.com>,
	Wolfgang Bumiller <w.bumiller@proxmox.com>,
	linux-mm@kvack.org, linux-kernel@vger.kernel.org
Subject: Re: segfaults of processes while being killed after commit "mm: make the page fault mmap locking killable"
Date: Thu, 27 Jul 2023 09:57:58 +0200	[thread overview]
Message-ID: <1eb5c9ca-0e05-7aab-c60e-33cc0d8a9323@proxmox.com> (raw)
In-Reply-To: <CAHk-=wivat-bcWsGnQOd3=ODx0zFnc7R82tiee=fSU+DF4tD5g@mail.gmail.com>

Am 26.07.23 um 19:59 schrieb Linus Torvalds:
> 
> It's commit 5f0bc0b042fc ("mm: suppress mm fault logging if fatal
> signal already pending") in my tree now.
> 
> And because it's a bit different from what you already tested, it
> would be lovely to just get a confirmation that I didn't screw
> anything up when I decided I needed to make a fix that covers more
> than just x86.
> 
I can confirm this still avoids the misleading logging for me :)

Thank you for the fix!

Best Regards,
Fiona



      reply	other threads:[~2023-07-27  7:58 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-25 11:16 segfaults of processes while being killed after commit "mm: make the page fault mmap locking killable" Fiona Ebner
2023-07-25 16:38 ` Linus Torvalds
2023-07-26  6:51   ` Thomas Lamprecht
2023-07-26  8:19   ` Fiona Ebner
2023-07-26 17:59     ` Linus Torvalds
2023-07-27  7:57       ` Fiona Ebner [this message]

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=1eb5c9ca-0e05-7aab-c60e-33cc0d8a9323@proxmox.com \
    --to=f.ebner@proxmox.com \
    --cc=akpm@linux-foundation.org \
    --cc=ebiederm@xmission.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=oleg@redhat.com \
    --cc=t.lamprecht@proxmox.com \
    --cc=torvalds@linux-foundation.org \
    --cc=w.bumiller@proxmox.com \
    /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;
as well as URLs for NNTP newsgroup(s).