From: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
To: Chuck Lever III <chuck.lever@oracle.com>
Cc: "linux-nfs@vger.kernel.org" <linux-nfs@vger.kernel.org>,
Trond Myklebust <trond.myklebust@hammerspace.com>,
Anna Schumaker <anna@kernel.org>,
Thomas Gleixner <tglx@linutronix.de>,
Mike Galbraith <umgwanakikbuti@gmail.com>
Subject: Re: [PATCH] SUNRPC: Don't disable preemption while calling svc_pool_for_cpu().
Date: Thu, 5 May 2022 08:26:13 +0200 [thread overview]
Message-ID: <YnNuBbh278TOJ81z@linutronix.de> (raw)
In-Reply-To: <C4463E0E-2886-47A2-B915-A008C35343A5@oracle.com>
On 2022-05-05 03:19:57 [+0000], Chuck Lever III wrote:
>
> Sebastian, I will have a closer look in a few days. Meanwhile, if I’m
> reading the patch description right, this is a bug fix. Was there a
> lockdep splat (ie, how did you find this issue)? Does it belong in
> 5.18-rc? Should it have a Fixes: tag?
It is a bugfix for PREEMPT_RT and I'm posting this as part of getting
PREEMPT_RT merged upstream. This is already fixed in the PREEMPT_RT
queue.
There is no need to get this merged in the current -rc series since
!PREEMPT_RT is not affected. Next release is fine.
Sebastian
next prev parent reply other threads:[~2022-05-05 6:26 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-04 17:24 [PATCH] SUNRPC: Don't disable preemption while calling svc_pool_for_cpu() Sebastian Andrzej Siewior
2022-05-05 3:19 ` Chuck Lever III
2022-05-05 6:26 ` Sebastian Andrzej Siewior [this message]
2022-05-09 16:56 ` Chuck Lever III
2022-05-10 12:02 ` Sebastian Andrzej Siewior
2022-05-10 13:38 ` Chuck Lever III
2022-05-10 14:38 ` [PATCH v2] " Sebastian Andrzej Siewior
2022-05-10 15:43 ` Chuck Lever III
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=YnNuBbh278TOJ81z@linutronix.de \
--to=bigeasy@linutronix.de \
--cc=anna@kernel.org \
--cc=chuck.lever@oracle.com \
--cc=linux-nfs@vger.kernel.org \
--cc=tglx@linutronix.de \
--cc=trond.myklebust@hammerspace.com \
--cc=umgwanakikbuti@gmail.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.