Re: [PATCH 2/2] fuse: wait for aborted connection before releasing last fuse_dev
Berkant Koc <[email protected]>
| Newsgroups | org.kernel.vger.io-uring,dev.linux.lists.fuse-devel,org.kernel.vger.linux-kernel |
|---|---|
| Message-ID | <[email protected]> |
On Mon, 18 May 2026 08:35:16 -0700, Joanne Koong <[email protected]> wrote: > Yes, on mainline the references are meant to be ring->fc, eg Confirmed, ring->fc on mainline. Reviewed-by recorded for Bernd's v6.14 backport path. Bernd has since published the full 4-patch series via B4-Relay at 18:37 CEST, rebased onto Miklos' for-next (base-commit 040d71ac6470). On that branch the fuse_chan abstraction is in place, so the teardown path uses ring->chan / chan->conn rather than ring->fc. The series stays as-is for for-next. Your inline diff is the basis for the mainline stable-backport once for-next lands. I will run the two-arm Tested-by against for-next-base 040d71ac6470 (KASAN + lockdep + kmemleak, async-teardown race + baseline) and report numbers on-thread. Assisted-by: Claude:claude-opus-4-7 berkoc-pipeline