From: Christian Brauner <brauner@kernel.org>
To: Mateusz Guzik <mjguzik@gmail.com>,
Linus Torvalds <torvalds@linux-foundation.org>
Cc: viro@zeniv.linux.org.uk, jack@suse.cz,
linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org
Subject: Re: [PATCH 1/2] lockref: speculatively spin waiting for the lock to be released
Date: Thu, 13 Jun 2024 15:46:04 +0200 [thread overview]
Message-ID: <20240613-pumpen-durst-fdc20c301a08@brauner> (raw)
In-Reply-To: <5cixyyivolodhsru23y5gf5f6w6ov2zs5rbkxleljeu6qvc4gu@ivawdfkvus3p>
> All that aside, you did not indicate how do you want to move forward
> regarding patch submission.
I've picked Linus patch and your for testing into the vfs.inode.rcu branch.
Was trivial to fix your typo and to add Linus as author with your commit
message. Let's see what syzbot and that perf bot have to say.
next prev parent reply other threads:[~2024-06-13 13:46 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-13 0:12 [PATCH 0/2] stop lockref from degrading to locked-only ops Mateusz Guzik
2024-06-13 0:12 ` [PATCH 1/2] lockref: speculatively spin waiting for the lock to be released Mateusz Guzik
2024-06-13 1:23 ` Linus Torvalds
2024-06-13 1:49 ` Linus Torvalds
2024-06-13 6:09 ` Mateusz Guzik
2024-06-13 13:46 ` Christian Brauner [this message]
2024-06-13 13:50 ` Mateusz Guzik
2024-06-13 17:00 ` Linus Torvalds
2024-06-13 18:13 ` Mateusz Guzik
2024-06-13 18:41 ` Mateusz Guzik
2024-06-13 18:43 ` Linus Torvalds
2024-06-13 18:47 ` Mateusz Guzik
2024-06-13 18:56 ` Linus Torvalds
2024-06-13 19:02 ` Mateusz Guzik
2024-06-13 19:33 ` Linus Torvalds
2024-06-18 12:11 ` Christian Brauner
2024-06-13 18:55 ` Al Viro
2024-06-13 16:50 ` Linus Torvalds
2024-06-13 0:12 ` [PATCH 2/2] vfs: move d_lockref out of the area used by RCU lookup Mateusz Guzik
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=20240613-pumpen-durst-fdc20c301a08@brauner \
--to=brauner@kernel.org \
--cc=jack@suse.cz \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mjguzik@gmail.com \
--cc=torvalds@linux-foundation.org \
--cc=viro@zeniv.linux.org.uk \
/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).