From: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
To: Valentin Schneider <vschneid@redhat.com>
Cc: linux-kernel@vger.kernel.org, kexec@lists.infradead.org,
linux-rt-users@vger.kernel.org,
Eric Biederman <ebiederm@xmission.com>,
Arnd Bergmann <arnd@arndb.de>, Petr Mladek <pmladek@suse.com>,
Thomas Gleixner <tglx@linutronix.de>,
Juri Lelli <jlelli@redhat.com>,
"Luis Claudio R. Goncalves" <lgoncalv@redhat.com>
Subject: Re: [PATCH v2] panic, kexec: Make __crash_kexec() NMI safe
Date: Thu, 23 Jun 2022 15:35:23 +0200 [thread overview]
Message-ID: <YrRsGzXTpms+FOeI@linutronix.de> (raw)
In-Reply-To: <xhsmhy1xn622a.mognet@vschneid.remote.csb>
On 2022-06-23 12:39:57 [+0100], Valentin Schneider wrote:
> > RT-wise it would be needed for each release.
>
> So git tells me the Fixes: commit dates from v4.2; from [1] and [2] I get
> that both current longterm stable and stable-rt trees go as far back as
> v4.9, so I'm guessing if that gets picked up for the stable trees then it
> should make its way into the stable -rt trees?
correct, if it goes -stable. Just pointing it out. But the
mutex_unlock() looks like it might also be relevant for non-RT kernels.
Sebastian
WARNING: multiple messages have this Message-ID (diff)
From: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
To: Valentin Schneider <vschneid@redhat.com>
Cc: linux-kernel@vger.kernel.org, kexec@lists.infradead.org,
linux-rt-users@vger.kernel.org,
Eric Biederman <ebiederm@xmission.com>,
Arnd Bergmann <arnd@arndb.de>, Petr Mladek <pmladek@suse.com>,
Thomas Gleixner <tglx@linutronix.de>,
Juri Lelli <jlelli@redhat.com>,
"Luis Claudio R. Goncalves" <lgoncalv@redhat.com>
Subject: Re: [PATCH v2] panic, kexec: Make __crash_kexec() NMI safe
Date: Thu, 23 Jun 2022 15:35:23 +0200 [thread overview]
Message-ID: <YrRsGzXTpms+FOeI@linutronix.de> (raw)
In-Reply-To: <xhsmhy1xn622a.mognet@vschneid.remote.csb>
On 2022-06-23 12:39:57 [+0100], Valentin Schneider wrote:
> > RT-wise it would be needed for each release.
>
> So git tells me the Fixes: commit dates from v4.2; from [1] and [2] I get
> that both current longterm stable and stable-rt trees go as far back as
> v4.9, so I'm guessing if that gets picked up for the stable trees then it
> should make its way into the stable -rt trees?
correct, if it goes -stable. Just pointing it out. But the
mutex_unlock() looks like it might also be relevant for non-RT kernels.
Sebastian
_______________________________________________
kexec mailing list
kexec@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kexec
next prev parent reply other threads:[~2022-06-23 13:35 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-20 11:15 [PATCH v2] panic, kexec: Make __crash_kexec() NMI safe Valentin Schneider
2022-06-20 11:15 ` Valentin Schneider
2022-06-23 9:31 ` Sebastian Andrzej Siewior
2022-06-23 9:31 ` Sebastian Andrzej Siewior
2022-06-23 11:39 ` Valentin Schneider
2022-06-23 11:39 ` Valentin Schneider
2022-06-23 13:35 ` Sebastian Andrzej Siewior [this message]
2022-06-23 13:35 ` Sebastian Andrzej Siewior
2022-06-24 1:30 ` Baoquan He
2022-06-24 1:30 ` Baoquan He
2022-06-24 13:37 ` Valentin Schneider
2022-06-24 13:37 ` Valentin Schneider
2022-06-26 10:37 ` Baoquan He
2022-06-26 10:37 ` Baoquan He
2022-06-26 10:45 ` Baoquan He
2022-06-26 10:45 ` Baoquan He
2022-06-25 17:04 ` Eric W. Biederman
2022-06-25 17:04 ` Eric W. Biederman
2022-06-27 12:42 ` Valentin Schneider
2022-06-27 12:42 ` Valentin Schneider
2022-06-28 17:33 ` Valentin Schneider
2022-06-28 17:33 ` Valentin Schneider
2022-06-29 11:55 ` Petr Mladek
2022-06-29 11:55 ` Petr Mladek
2022-06-29 12:23 ` Valentin Schneider
2022-06-29 12:23 ` Valentin Schneider
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=YrRsGzXTpms+FOeI@linutronix.de \
--to=bigeasy@linutronix.de \
--cc=arnd@arndb.de \
--cc=ebiederm@xmission.com \
--cc=jlelli@redhat.com \
--cc=kexec@lists.infradead.org \
--cc=lgoncalv@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rt-users@vger.kernel.org \
--cc=pmladek@suse.com \
--cc=tglx@linutronix.de \
--cc=vschneid@redhat.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 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.