From: Christian Brauner <brauner@kernel.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-fsdevel@vger.kernel.org,
Thomas Gleixner <tglx@linutronix.de>,
Jann Horn <jannh@google.com>
Subject: Re: [PATCH RFC 0/4] fs: port files to rcuref_long_t
Date: Sun, 6 Oct 2024 12:21:27 +0200 [thread overview]
Message-ID: <20241006-textzeilen-liehen-2e3083bd60bb@brauner> (raw)
In-Reply-To: <CAHk-=wgwPwrao9Bq2SKDExPHXJAYO2QD1F-0C6JMtSaE1_T_ag@mail.gmail.com>
On Sat, Oct 05, 2024 at 03:01:45PM GMT, Linus Torvalds wrote:
> On Sat, 5 Oct 2024 at 14:42, Linus Torvalds
> <torvalds@linux-foundation.org> wrote:
> >
> > and I think that might work, although the zero count case worries me
> > (ie 'fput twice').
> >
> > Currently we avoid the fput twice because we use that
> > "inc_not_zero()". So that needs some thinking about.
>
> Actually, it's worse. Even the
>
> if (ret > 1)
>
> case is dangerous, because we could have two or more threads doing
> that atomic_inc_return() on a dead file descriptor at the same time.
>
> So that approach is just broken.
Iiuc, then we should retain the deadzone handling but should replace
atomic_long_add_negative() with atomic_long_add_negative_relaxed().
So I would add:
static inline __must_check bool rcuref_long_inc(rcuref_long_t *ref)
{
/*
* Unconditionally increase the reference count with full
* ordering. The saturation and dead zones provide enough
* tolerance for this.
*/
if (likely(!atomic_long_add_negative(1, &ref->refcnt)))
return true;
/* Handle the cases inside the saturation and dead zones */
return rcuref_long_get_slowpath(ref);
}
Or did I miss something else?
next prev parent reply other threads:[~2024-10-06 10:21 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-05 19:16 [PATCH RFC 0/4] fs: port files to rcuref_long_t Christian Brauner
2024-10-05 19:16 ` [PATCH RFC 1/4] fs: protect backing files with rcu Christian Brauner
2024-10-05 19:16 ` [PATCH RFC 2/4] types: add rcuref_long_t Christian Brauner
2024-10-05 19:16 ` [PATCH RFC 3/4] rcuref: add rcuref_long_*() helpers Christian Brauner
2024-10-05 19:16 ` [PATCH RFC 4/4] fs: port files to rcuref_long_t Christian Brauner
2024-10-05 21:42 ` [PATCH RFC 0/4] " Linus Torvalds
2024-10-05 22:01 ` Al Viro
2024-10-05 22:14 ` Linus Torvalds
2024-10-05 22:28 ` Al Viro
2024-10-05 22:43 ` Linus Torvalds
2024-10-05 22:51 ` Al Viro
2024-10-06 9:55 ` Christian Brauner
2024-10-05 22:01 ` Linus Torvalds
2024-10-06 10:21 ` Christian Brauner [this message]
2024-10-06 18:09 ` Linus Torvalds
2024-10-07 7:37 ` Christian Brauner
2024-10-06 9:48 ` Christian Brauner
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=20241006-textzeilen-liehen-2e3083bd60bb@brauner \
--to=brauner@kernel.org \
--cc=jannh@google.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=tglx@linutronix.de \
--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;
as well as URLs for NNTP newsgroup(s).