[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20251005174010.GC6063@redhat.com>
Date: Sun, 5 Oct 2025 19:40:11 +0200
From: Oleg Nesterov <oleg@...hat.com>
To: Al Viro <viro@...iv.linux.org.uk>
Cc: Boqun Feng <boqun.feng@...il.com>, David Howells <dhowells@...hat.com>,
Ingo Molnar <mingo@...hat.com>, Li RongQing <lirongqing@...du.com>,
Linus Torvalds <torvalds@...ux-foundation.org>,
Peter Zijlstra <peterz@...radead.org>,
Waiman Long <longman@...hat.com>, Will Deacon <will@...nel.org>,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH 0/5] seqlock: introduce SEQLOCK_READ_SECTION()
On 10/05, Al Viro wrote:
>
> On Sun, Oct 05, 2025 at 04:49:29PM +0200, Oleg Nesterov wrote:
>
> > static char *__dentry_path(const struct dentry *d, struct prepend_buffer *p)
> > {
> > const struct dentry *dentry;
> > struct prepend_buffer b;
> >
> > rcu_read_lock();
> > __SEQLOCK_READ_SECTION(&rename_lock, lockless, seq, NULL) {
> > dentry = d;
> > b = *p;
> > while (!IS_ROOT(dentry)) {
> > const struct dentry *parent = dentry->d_parent;
> >
> > prefetch(parent);
> > if (!prepend_name(&b, &dentry->d_name))
> > break;
> > dentry = parent;
> > }
> > if (lockless)
> > rcu_read_unlock();
>
> <cringe>
Weird or buggy?
> prepend_path() would be interesting to look at...
Yeah, I have already looked at it.
Not sure yet what the "good" cleanup could do. Will think about it more.
Oleg.
Powered by blists - more mailing lists