Re: [BUG REPORT] linux-next/fs-next released on 6th September fails to boot

[Chandan Babu R <chandanbabu@kernel.org>]

On Mon, Sep 09, 2024 at 05:56:11 PM +0200, Alexander Mikhalitsyn wrote:
> Dear Chandan,
>
> Please can you check if the following patch resolves issue for your workload:
>
> diff --git a/fs/fuse/dev.c b/fs/fuse/dev.c
> index 7885f071fa1e..f130b23d6850 100644
> --- a/fs/fuse/dev.c
> +++ b/fs/fuse/dev.c
> @@ -148,7 +148,7 @@ static struct fuse_req *fuse_get_req(struct
> mnt_idmap *idmap,
>         if (for_background)
>                 __set_bit(FR_BACKGROUND, &req->flags);
>
> -       if ((fm->sb->s_iflags & SB_I_NOIDMAP) || idmap) {
> +       if (!fm->sb || (fm->sb->s_iflags & SB_I_NOIDMAP) || idmap) {
>                 kuid_t idmapped_fsuid;
>                 kgid_t idmapped_fsgid;
>
> From your call stack if looks caused by CUSE case.
> It's my bad that I have not considered this use case for
> fuse_get_req() and there is, obviously,
> no such thing as fm->sb for CUSE scenario.
>

The above patch solves the problem. Thank you!

-- 
Chandan