public inbox for stable@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Leah Rumancik <leah.rumancik@gmail.com>
Cc: stable@vger.kernel.org, miklos@szeredi.hu,
	Murphy Zhou <jencce.kernel@gmail.com>,
	Miklos Szeredi <mszeredi@redhat.com>
Subject: Re: [PATCH] ovl: add splice file read write helper
Date: Sat, 21 Aug 2021 13:29:03 +0200	[thread overview]
Message-ID: <YSDjf8yeYkkMQty9@kroah.com> (raw)
In-Reply-To: <20210820195929.1926705-1-leah.rumancik@gmail.com>

On Fri, Aug 20, 2021 at 07:59:29PM +0000, Leah Rumancik wrote:
> From: Murphy Zhou <jencce.kernel@gmail.com>
> 
> Now overlayfs falls back to use default file splice read
> and write, which is not compatiple with overlayfs, returning
> EFAULT. xfstests generic/591 can reproduce part of this.
> 
> Tested this patch with xfstests auto group tests.
> 
> [ Needed in 5.4 to fix a deadlock triggered via
>   xfstests overlay/019 -- Leah Rumancik ]
> 
> Signed-off-by: Murphy Zhou <jencce.kernel@gmail.com>
> Signed-off-by: Miklos Szeredi <mszeredi@redhat.com>
> ---
>  fs/overlayfs/file.c | 47 +++++++++++++++++++++++++++++++++++++++++++++
>  1 file changed, 47 insertions(+)
> 

<formletter>

This is not the correct way to submit patches for inclusion in the
stable kernel tree.  Please read:
    https://www.kernel.org/doc/html/latest/process/stable-kernel-rules.html
for how to do this properly.

</formletter>

  reply	other threads:[~2021-08-21 11:29 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-08-20 19:59 [PATCH] ovl: add splice file read write helper Leah Rumancik
2021-08-21 11:29 ` Greg KH [this message]
2021-08-23  0:54 ` Sasha Levin

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=YSDjf8yeYkkMQty9@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=jencce.kernel@gmail.com \
    --cc=leah.rumancik@gmail.com \
    --cc=miklos@szeredi.hu \
    --cc=mszeredi@redhat.com \
    --cc=stable@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox