From: Luis Henriques <lhenriques@suse.com>
To: "Yan\, Zheng" <zyan@redhat.com>
Cc: Sage Weil <sage@redhat.com>, Ilya Dryomov <idryomov@gmail.com>,
ceph-devel@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] ceph: check negative offsets on ceph_llseek()
Date: Thu, 17 Aug 2017 14:45:49 +0100 [thread overview]
Message-ID: <87pobuz4s2.fsf@hermes> (raw)
In-Reply-To: <20170728105640.16268-1-lhenriques@suse.com> (Luis Henriques's message of "Fri, 28 Jul 2017 11:56:40 +0100")
Luis Henriques <lhenriques@suse.com> writes:
> When a user requests SEEK_HOLE or SEEK_DATA with a negative offset
> ceph_llseek should return -ENXIO. Currently -EINVAL is being returned for
> SEEK_DATA and 0 for SEEK_HOLE.
Ping
This patch should make xfstest generic/448 happy.
Cheers,
--
Luís
>
> Signed-off-by: Luis Henriques <lhenriques@suse.com>
> ---
> fs/ceph/file.c | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/fs/ceph/file.c b/fs/ceph/file.c
> index 3d48c415f3cb..e1912e67843f 100644
> --- a/fs/ceph/file.c
> +++ b/fs/ceph/file.c
> @@ -1481,13 +1481,13 @@ static loff_t ceph_llseek(struct file *file, loff_t offset, int whence)
> offset += file->f_pos;
> break;
> case SEEK_DATA:
> - if (offset >= i_size) {
> + if (offset < 0 || offset >= i_size) {
> ret = -ENXIO;
> goto out;
> }
> break;
> case SEEK_HOLE:
> - if (offset >= i_size) {
> + if (offset < 0 || offset >= i_size) {
> ret = -ENXIO;
> goto out;
> }
>
next prev parent reply other threads:[~2017-08-17 13:46 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-28 10:56 [PATCH] ceph: check negative offsets on ceph_llseek() Luis Henriques
2017-08-17 13:45 ` Luis Henriques [this message]
2017-08-17 17:57 ` Ilya Dryomov
2017-08-17 18:40 ` Luis Henriques
2017-08-18 8:32 ` Ilya Dryomov
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=87pobuz4s2.fsf@hermes \
--to=lhenriques@suse.com \
--cc=ceph-devel@vger.kernel.org \
--cc=idryomov@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=sage@redhat.com \
--cc=zyan@redhat.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox