[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20251129035510.GI3538@ZenIV>
Date: Sat, 29 Nov 2025 03:55:10 +0000
From: Al Viro <viro@...iv.linux.org.uk>
To: Zizhi Wo <wozizhi@...weicloud.com>
Cc: Will Deacon <will@...nel.org>,
Linus Torvalds <torvalds@...ux-foundation.org>, jack@...e.com,
brauner@...nel.org, hch@....de, akpm@...ux-foundation.org,
linux@...linux.org.uk, linux-fsdevel@...r.kernel.org,
linux-kernel@...r.kernel.org, linux-mm@...ck.org,
linux-arm-kernel@...ts.infradead.org, yangerkun@...wei.com,
wangkefeng.wang@...wei.com, pangliyuan1@...wei.com,
xieyuanbin1@...wei.com
Subject: Re: [Bug report] hash_name() may cross page boundary and trigger
sleep in RCU context
On Sat, Nov 29, 2025 at 09:02:27AM +0800, Zizhi Wo wrote:
> Thank you very much for the answer. For the vmalloc area, I checked the
> call points on the vfs side, such as dentry_string_cmp() or hash_name().
> Their "names addr" are all assigned by kmalloc(), so there should be no
> corresponding issues. But I'm not familiar with the other calling
> points...
Pathname might be a symlink body, sitting in page cache or whatever
->get_link() has returned...
Powered by blists - more mailing lists