* FAILED: patch "[PATCH] fuse: release pipe buf after last use" failed to apply to 4.9-stable tree
@ 2021-11-27 13:10 gregkh
2021-11-29 15:46 ` Miklos Szeredi
0 siblings, 1 reply; 3+ messages in thread
From: gregkh @ 2021-11-27 13:10 UTC (permalink / raw)
To: mszeredi, jmforbes, stable; +Cc: stable
The patch below does not apply to the 4.9-stable tree.
If someone wants it applied there, or to any other stable or longterm
tree, then please email the backport, including the original git commit
id to <stable@vger.kernel.org>.
thanks,
greg k-h
------------------ original commit in Linus's tree ------------------
From 473441720c8616dfaf4451f9c7ea14f0eb5e5d65 Mon Sep 17 00:00:00 2001
From: Miklos Szeredi <mszeredi@redhat.com>
Date: Thu, 25 Nov 2021 14:05:18 +0100
Subject: [PATCH] fuse: release pipe buf after last use
Checking buf->flags should be done before the pipe_buf_release() is called
on the pipe buffer, since releasing the buffer might modify the flags.
This is exactly what page_cache_pipe_buf_release() does, and which results
in the same VM_BUG_ON_PAGE(PageLRU(page)) that the original patch was
trying to fix.
Reported-by: Justin Forbes <jmforbes@linuxtx.org>
Fixes: 712a951025c0 ("fuse: fix page stealing")
Cc: <stable@vger.kernel.org> # v2.6.35
Signed-off-by: Miklos Szeredi <mszeredi@redhat.com>
diff --git a/fs/fuse/dev.c b/fs/fuse/dev.c
index 79f7eda49e06..cd54a529460d 100644
--- a/fs/fuse/dev.c
+++ b/fs/fuse/dev.c
@@ -847,17 +847,17 @@ static int fuse_try_move_page(struct fuse_copy_state *cs, struct page **pagep)
replace_page_cache_page(oldpage, newpage);
+ get_page(newpage);
+
+ if (!(buf->flags & PIPE_BUF_FLAG_LRU))
+ lru_cache_add(newpage);
+
/*
* Release while we have extra ref on stolen page. Otherwise
* anon_pipe_buf_release() might think the page can be reused.
*/
pipe_buf_release(cs->pipe, buf);
- get_page(newpage);
-
- if (!(buf->flags & PIPE_BUF_FLAG_LRU))
- lru_cache_add(newpage);
-
err = 0;
spin_lock(&cs->req->waitq.lock);
if (test_bit(FR_ABORTED, &cs->req->flags))
^ permalink raw reply related [flat|nested] 3+ messages in thread
* Re: FAILED: patch "[PATCH] fuse: release pipe buf after last use" failed to apply to 4.9-stable tree
2021-11-27 13:10 FAILED: patch "[PATCH] fuse: release pipe buf after last use" failed to apply to 4.9-stable tree gregkh
@ 2021-11-29 15:46 ` Miklos Szeredi
2021-11-29 16:12 ` Greg Kroah-Hartman
0 siblings, 1 reply; 3+ messages in thread
From: Miklos Szeredi @ 2021-11-29 15:46 UTC (permalink / raw)
To: Greg Kroah-Hartman; +Cc: Justin Forbes, stable
[-- Attachment #1: Type: text/plain, Size: 442 bytes --]
On Sat, Nov 27, 2021 at 2:11 PM <gregkh@linuxfoundation.org> wrote:
>
>
> The patch below does not apply to the 4.9-stable tree.
> If someone wants it applied there, or to any other stable or longterm
> tree, then please email the backport, including the original git commit
> id to <stable@vger.kernel.org>.
Hi Greg,
Attaching the backport against 4.9.292-rc1.
Should apply to the 4.14, 4.19 and 5.4 stable trees as well.
Thanks,
Miklos
[-- Attachment #2: fuse-release-pipe-buf-after-last-use-4.9.patch --]
[-- Type: text/x-patch, Size: 1586 bytes --]
From d84c327c0f8163524407c9f182710b1d9cefb930 Mon Sep 17 00:00:00 2001
From: Miklos Szeredi <mszeredi@redhat.com>
Date: Thu, 25 Nov 2021 14:05:18 +0100
Subject: [PATCH] fuse: release pipe buf after last use
Checking buf->flags should be done before the pipe_buf_release() is called
on the pipe buffer, since releasing the buffer might modify the flags.
This is exactly what page_cache_pipe_buf_release() does, and which results
in the same VM_BUG_ON_PAGE(PageLRU(page)) that the original patch was
trying to fix.
Reported-by: Justin Forbes <jmforbes@linuxtx.org>
Fixes: 712a951025c0 ("fuse: fix page stealing")
Cc: <stable@vger.kernel.org> # v2.6.35
Signed-off-by: Miklos Szeredi <mszeredi@redhat.com>
(cherry picked from commit 473441720c8616dfaf4451f9c7ea14f0eb5e5d65)
---
fs/fuse/dev.c | 10 +++++-----
1 file changed, 5 insertions(+), 5 deletions(-)
diff --git a/fs/fuse/dev.c b/fs/fuse/dev.c
index 72ce66e0e08c..585c52dbb2e3 100644
--- a/fs/fuse/dev.c
+++ b/fs/fuse/dev.c
@@ -898,17 +898,17 @@ static int fuse_try_move_page(struct fuse_copy_state *cs, struct page **pagep)
goto out_put_old;
}
+ get_page(newpage);
+
+ if (!(buf->flags & PIPE_BUF_FLAG_LRU))
+ lru_cache_add_file(newpage);
+
/*
* Release while we have extra ref on stolen page. Otherwise
* anon_pipe_buf_release() might think the page can be reused.
*/
pipe_buf_release(cs->pipe, buf);
- get_page(newpage);
-
- if (!(buf->flags & PIPE_BUF_FLAG_LRU))
- lru_cache_add_file(newpage);
-
err = 0;
spin_lock(&cs->req->waitq.lock);
if (test_bit(FR_ABORTED, &cs->req->flags))
--
2.31.1
^ permalink raw reply related [flat|nested] 3+ messages in thread
* Re: FAILED: patch "[PATCH] fuse: release pipe buf after last use" failed to apply to 4.9-stable tree
2021-11-29 15:46 ` Miklos Szeredi
@ 2021-11-29 16:12 ` Greg Kroah-Hartman
0 siblings, 0 replies; 3+ messages in thread
From: Greg Kroah-Hartman @ 2021-11-29 16:12 UTC (permalink / raw)
To: Miklos Szeredi; +Cc: Justin Forbes, stable
On Mon, Nov 29, 2021 at 04:46:34PM +0100, Miklos Szeredi wrote:
> On Sat, Nov 27, 2021 at 2:11 PM <gregkh@linuxfoundation.org> wrote:
> >
> >
> > The patch below does not apply to the 4.9-stable tree.
> > If someone wants it applied there, or to any other stable or longterm
> > tree, then please email the backport, including the original git commit
> > id to <stable@vger.kernel.org>.
>
> Hi Greg,
>
> Attaching the backport against 4.9.292-rc1.
>
> Should apply to the 4.14, 4.19 and 5.4 stable trees as well.
Wonderful, thanks for this, now queued up.
greg k-h
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2021-11-29 16:14 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2021-11-27 13:10 FAILED: patch "[PATCH] fuse: release pipe buf after last use" failed to apply to 4.9-stable tree gregkh
2021-11-29 15:46 ` Miklos Szeredi
2021-11-29 16:12 ` Greg Kroah-Hartman
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.