From: David Howells <dhowells@redhat.com>
To: Oleg Nesterov <oleg@redhat.com>
Cc: dhowells@redhat.com, Christian Brauner <christian@brauner.io>,
Marc Dionne <marc.dionne@auristor.com>,
linux-afs@lists.infradead.org, linux-fsdevel@vger.kernel.org,
linux-kernel@vger.kernel.org, Li RongQing <lirongqing@baidu.com>
Subject: Re: [PATCH 6/7] afs: Remove erroneous seq |= 1 in volume lookup loop
Date: Tue, 09 Jun 2026 16:53:05 +0100 [thread overview]
Message-ID: <872443.1781020385@warthog.procyon.org.uk> (raw)
In-Reply-To: <aifaeKvz3KemfzaS@redhat.com>
Oleg Nesterov <oleg@redhat.com> wrote:
> Yes, but now that we have scoped_seqlock_read() we can make another change
> on top of this fix. afs_lookup_volume_rcu() can just do
I wonder if that would be better as a separate patch rather than merged into
this one.
David
next prev parent reply other threads:[~2026-06-09 15:53 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-09 8:17 [PATCH 0/7] afs: Miscellaneous fixes David Howells
2026-06-09 8:17 ` [PATCH 1/7] afs: handle CB.InitCallBackState3 requests without a server record David Howells
2026-06-09 8:17 ` [PATCH 2/7] afs: Fix error code in afs_extract_vl_addrs() David Howells
2026-06-09 8:17 ` [PATCH 3/7] afs: fix NULL pointer dereference in afs_get_tree() David Howells
2026-06-09 8:17 ` [PATCH 4/7] afs: Remove setting of AS_RELEASE_ALWAYS for symlinks and mountpoints David Howells
2026-06-09 8:17 ` [PATCH 5/7] afs: use kvfree() to free memory allocated by kvcalloc() David Howells
2026-06-09 8:17 ` [PATCH 6/7] afs: Remove erroneous seq |= 1 in volume lookup loop David Howells
2026-06-09 9:18 ` Oleg Nesterov
2026-06-09 15:53 ` David Howells [this message]
2026-06-09 16:43 ` Jeffrey E Altman
2026-06-09 8:17 ` [PATCH 7/7] afs: check for duplicate servers in VL server list David Howells
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=872443.1781020385@warthog.procyon.org.uk \
--to=dhowells@redhat.com \
--cc=christian@brauner.io \
--cc=linux-afs@lists.infradead.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lirongqing@baidu.com \
--cc=marc.dionne@auristor.com \
--cc=oleg@redhat.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®