[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAJfpegvGhtLSxOHUQQ95a3skqEgEPt+MzpBT8vOOdqWcRxPR5Q@mail.gmail.com>
Date: Wed, 8 May 2024 10:21:14 +0200
From: Miklos Szeredi <miklos@...redi.hu>
To: Hou Tao <houtao@...weicloud.com>
Cc: lee bruce <xrivendell7@...il.com>, linux-fsdevel@...r.kernel.org,
yue sun <samsun1006219@...il.com>, linux-kernel@...r.kernel.org,
syzkaller@...glegroups.com
Subject: Re: WARNING in fuse_request_end
On Tue, 7 May 2024 at 15:30, Hou Tao <houtao@...weicloud.com> wrote:
> diff --git a/fs/fuse/dev.c b/fs/fuse/dev.c
> index 3ec8bb5e68ff5..840cefdf24e26 100644
> --- a/fs/fuse/dev.c
> +++ b/fs/fuse/dev.c
> @@ -1814,6 +1814,7 @@ static void fuse_resend(struct fuse_conn *fc)
>
> list_for_each_entry_safe(req, next, &to_queue, list) {
> __set_bit(FR_PENDING, &req->flags);
> + clear_bit(FR_SENT, &req->flags);
> /* mark the request as resend request */
> req->in.h.unique |= FUSE_UNIQUE_RESEND;
> }
>
ACK, fix looks good.
Would you mind resending it as a proper patch?
Thanks,
Miklos
Powered by blists - more mailing lists