All of lore.kernel.org
 help / color / mirror / Atom feed
From: Yang Xu <xuyang2018.jy@cn.fujitsu.com>
To: guaneryu@gmail.com, amir73il@gmail.com
Cc: fstests@vger.kernel.org, Yang Xu <xuyang2018.jy@cn.fujitsu.com>
Subject: [PATCH] generic/553[4]: correct kernel fix commit
Date: Wed, 10 Jul 2019 19:35:22 +0800	[thread overview]
Message-ID: <1562758522-6359-1-git-send-email-xuyang2018.jy@cn.fujitsu.com> (raw)

commit 96e6e8f4a68d ("vfs: add missing checks to copy_file_range")
adds checks for immutablefile and swapfile instead of commit a31713517d
("vfs: introduce generic_file_rw_checks()").

Signed-off-by: Yang Xu <xuyang2018.jy@cn.fujitsu.com>
---
 tests/generic/553 | 2 +-
 tests/generic/554 | 2 +-
 2 files changed, 2 insertions(+), 2 deletions(-)

diff --git a/tests/generic/553 b/tests/generic/553
index aefb0819..a836e602 100755
--- a/tests/generic/553
+++ b/tests/generic/553
@@ -7,7 +7,7 @@
 # Check that we cannot copy_file_range() to an immutable file
 #
 # This is a regression test for kernel commit:
-#   a31713517dac ("vfs: introduce generic_file_rw_checks()")
+#   96e6e8f4a68d ("vfs: add missing checks to copy_file_range")
 #
 seq=`basename $0`
 seqres=$RESULT_DIR/$seq
diff --git a/tests/generic/554 b/tests/generic/554
index fa19d580..eaf1f45a 100755
--- a/tests/generic/554
+++ b/tests/generic/554
@@ -7,7 +7,7 @@
 # Check that we cannot copy_file_range() to a swapfile
 #
 # This is a regression test for kernel commit:
-#   a31713517dac ("vfs: introduce generic_file_rw_checks()")
+#   96e6e8f4a68d ("vfs: add missing checks to copy_file_range")
 #
 seq=`basename $0`
 seqres=$RESULT_DIR/$seq
-- 
2.18.1

             reply	other threads:[~2019-07-11  5:24 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-07-10 11:35 Yang Xu [this message]
2019-07-11  6:50 ` [PATCH] generic/553[4]: correct kernel fix commit Amir Goldstein

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=1562758522-6359-1-git-send-email-xuyang2018.jy@cn.fujitsu.com \
    --to=xuyang2018.jy@cn.fujitsu.com \
    --cc=amir73il@gmail.com \
    --cc=fstests@vger.kernel.org \
    --cc=guaneryu@gmail.com \
    /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 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.