From: Christian Brauner <brauner@kernel.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [GIT PULL] fs preempt_rt fix
Date: Wed, 23 Mar 2022 12:02:49 +0100 [thread overview]
Message-ID: <20220323110248.858156-1-brauner@kernel.org> (raw)
Hey Linus,
/* Summary */
This contains Sebastian's fix to make changing mount attributes/getting write
access compatible with CONFIG_PREEMPT_RT. The change only applies when users
explicitly opt-in to real-time via CONFIG_PREEMPT_RT otherwise things are
exactly as before. We've waited quite a long time with this to make sure folks
could take a good look.
/* Testing */
All patches are based on v5.16-rc2 and have been sitting in linux-next. No
build failures or warnings were observed and fstests and selftests have seen no
regressions caused by this patchset.
/* Conflicts */
At the time of creating this PR no merge conflicts were reported from
linux-next and no merge conflicts showed up doing a test-merge with current
mainline.
The following changes since commit 136057256686de39cc3a07c2e39ef6bc43003ff6:
Linux 5.16-rc2 (2021-11-21 13:47:39 -0800)
are available in the Git repository at:
git@gitolite.kernel.org:pub/scm/linux/kernel/git/brauner/linux tags/fs.rt.v5.18
for you to fetch changes up to 0f8821da48458982cf379eb4432f23958f2e3a6c:
fs/namespace: Boost the mount_lock.lock owner instead of spinning on PREEMPT_RT. (2021-11-26 12:09:09 +0100)
Please consider pulling these changes from the signed fs.rt.v5.18 tag.
Thanks!
Christian
----------------------------------------------------------------
fs.rt.v5.18
----------------------------------------------------------------
Sebastian Andrzej Siewior (1):
fs/namespace: Boost the mount_lock.lock owner instead of spinning on PREEMPT_RT.
fs/namespace.c | 20 ++++++++++++++++++--
1 file changed, 18 insertions(+), 2 deletions(-)
next reply other threads:[~2022-03-23 11:03 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-23 11:02 Christian Brauner [this message]
2022-03-24 19:44 ` [GIT PULL] fs preempt_rt fix pr-tracker-bot
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=20220323110248.858156-1-brauner@kernel.org \
--to=brauner@kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox