mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Shuah Khan <skhan@linuxfoundation.org>
To: Kees Cook <keescook@chromium.org>, Shuah Khan <shuah@kernel.org>
Cc: kernel test robot <rong.a.chen@intel.com>,
	Christoph Hellwig <hch@lst.de>,
	linux-kselftest@vger.kernel.org,
	Al Viro <viro@zeniv.linux.org.uk>,
	linux-kernel@vger.kernel.org,
	Shuah Khan <skhan@linuxfoundation.org>
Subject: Re: [PATCH][RESEND] selftests: splice: Adjust for handler fallback removal
Date: Fri, 4 Jun 2021 15:33:13 -0600	[thread overview]
Message-ID: <db164ec1-6819-58cc-2ec0-8c6ff7bf0770@linuxfoundation.org> (raw)
In-Reply-To: <20210527032537.3730425-1-keescook@chromium.org>

On 5/26/21 9:25 PM, Kees Cook wrote:
> Some pseudo-filesystems do not have an explicit splice fops since adding
> commit 36e2c7421f02 ("fs: don't allow splice read/write without explicit ops"),
> and now will reject attempts to use splice() in those filesystem paths.
> 
> Reported-by: kernel test robot <rong.a.chen@intel.com>
> Link: https://lore.kernel.org/lkml/202009181443.C2179FB@keescook/
> Fixes: 36e2c7421f02 ("fs: don't allow splice read/write without explicit ops")
> Cc: Christoph Hellwig <hch@lst.de>
> Cc: Shuah Khan <shuah@kernel.org>
> Cc: linux-kselftest@vger.kernel.org
> Signed-off-by: Kees Cook <keescook@chromium.org>
> ---
> Resend of https://lore.kernel.org/linux-kselftest/20201005204517.2652730-1-keescook@chromium.org/
> ---
>   .../selftests/splice/short_splice_read.sh     | 119 ++++++++++++++----
>   1 file changed, 98 insertions(+), 21 deletions(-)

Will pick this up for 5.14

thanks,
-- Shuah

      reply	other threads:[~2021-06-04 21:34 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-27  3:25 Kees Cook
2021-06-04 21:33 ` Shuah Khan [this message]

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=db164ec1-6819-58cc-2ec0-8c6ff7bf0770@linuxfoundation.org \
    --to=skhan@linuxfoundation.org \
    --cc=hch@lst.de \
    --cc=keescook@chromium.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-kselftest@vger.kernel.org \
    --cc=rong.a.chen@intel.com \
    --cc=shuah@kernel.org \
    --cc=viro@zeniv.linux.org.uk \
    /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

all inboxes | Powered by JetHome®