From: David Hildenbrand <david@redhat.com>
To: "Jason A. Donenfeld" <Jason@zx2c4.com>,
linux-kernel@vger.kernel.org, gregkh@linuxfoundation.org
Cc: Tetsuo Handa <penguin-kernel@I-love.SAKURA.ne.jp>
Subject: Re: [PATCH] /dev/[k]mem: make reads and writes interruptible
Date: Thu, 7 Apr 2022 10:14:40 +0200 [thread overview]
Message-ID: <d7b928b9-7be1-f129-ff03-6ec9fe083f34@redhat.com> (raw)
In-Reply-To: <20220407001327.109095-1-Jason@zx2c4.com>
On 07.04.22 02:13, Jason A. Donenfeld wrote:
> In 8619e5bdeee8 ("/dev/mem: Bail out upon SIGKILL."), /dev/[k]mem became
> killable, and that commit noted:
>
> Theoretically, reading/writing /dev/mem and /dev/kmem can become
> "interruptible". But this patch chose "killable". Future patch will
> make them "interruptible" so that we can revert to "killable" if
> some program regressed.
>
> So now we take the next step in making it "interruptible", by changing
> fatal_signal_pending() into signal_pending().
/dev/kmem is no more. So this should only apply to /dev/mem nowadays.
--
Thanks,
David / dhildenb
next prev parent reply other threads:[~2022-04-07 8:14 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-07 0:13 [PATCH] /dev/[k]mem: make reads and writes interruptible Jason A. Donenfeld
2022-04-07 8:14 ` David Hildenbrand [this message]
2022-04-07 12:26 ` [PATCH v2] /dev/mem: " Jason A. Donenfeld
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=d7b928b9-7be1-f129-ff03-6ec9fe083f34@redhat.com \
--to=david@redhat.com \
--cc=Jason@zx2c4.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=penguin-kernel@I-love.SAKURA.ne.jp \
/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).