From: Al Viro <viro@zeniv.linux.org.uk>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Mateusz Guzik <mjguzik@gmail.com>,
Christian Brauner <brauner@kernel.org>,
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 19:55:45 +0100 [thread overview]
Message-ID: <20240613185545.GI1629371@ZenIV> (raw)
In-Reply-To: <CAHk-=wi4xCJKiCRzmDDpva+VhsrBuZfawGFb9vY6QXV2-_bELw@mail.gmail.com>
On Thu, Jun 13, 2024 at 11:43:05AM -0700, Linus Torvalds wrote:
> seqcount_spinlock_t d_seq;
>
> because seqcount_spinlock_t has been entirely broken and went from
> being 4 bytes back when, to now being 64 bytes.
1ca7d67cf5d5 "seqcount: Add lockdep functionality to seqcount/seqlock structures"
next prev parent reply other threads:[~2024-06-13 18:55 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
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 [this message]
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=20240613185545.GI1629371@ZenIV \
--to=viro@zeniv.linux.org.uk \
--cc=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 \
/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.