Date: Fri, 5 Sep 2025 03:14:43 +0300 From: Konstantin Belousov <kostikbel@gmail.com> To: obiwac <obiwac@freebsd.org> Cc: freebsd-current@freebsd.org, freebsd-fs@freebsd.org, alan.somers@freebsd.org Subject: Re: Fuse issue with attr caching expecting write lock Message-ID: <aLorc9rz87dibsQL@kib.kiev.ua> In-Reply-To: <CAN8-kNV6-H_YtmT2MeYkYOPcgcWrpe2K9jxqdb%2BjRzOJuk=-dA@mail.gmail.com>
index | next in thread | previous in thread | raw e-mail
On Fri, Sep 05, 2025 at 01:36:39AM +0200, obiwac wrote: > Hi! > > When trying to access a large file with sshfs (on fuse), I get a > kernel panic because fuse_internal_cache_attrs is asserting a write > lock when it is sometimes being called from fuse_internal_do_getattr, > which only asserts a read lock. > > To me (i.e. someone who has never touched VFS or fuse code) this code > looks wrong, and fuse_internal_do_getattr should be acquiring a write > lock around its call to fuse_internal_cache_attrs, but clearly it has > been working just fine for a while now as this code hasn't changed > super recently so I could be missing something. It is only the assertions that were enabled recently. Mark merged DEBUG_VFS_LOCKS option into INVARIANTS.home | help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?aLorc9rz87dibsQL>