From: Luis Henriques <lhenriques@suse.com>
To: Ilya Dryomov <idryomov@gmail.com>
Cc: "Yan, Zheng" <zyan@redhat.com>, Sage Weil <sage@redhat.com>,
Ceph Development <ceph-devel@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] ceph: check negative offsets on ceph_llseek()
Date: Thu, 17 Aug 2017 19:40:39 +0100 [thread overview]
Message-ID: <87lgmixck8.fsf@hermes> (raw)
In-Reply-To: <CAOi1vP9RYiFuscyJqetRO3p68Bj14To5whwM6EByvtjChCk0_g@mail.gmail.com> (Ilya Dryomov's message of "Thu, 17 Aug 2017 19:57:01 +0200")
Ilya Dryomov <idryomov@gmail.com> writes:
> On Thu, Aug 17, 2017 at 3:45 PM, Luis Henriques <lhenriques@suse.com> wrote:
>> 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.
>
> It should or it does? ;)
>
Heh, it *does* make generic/448 happy.
>
> I saw generic/448 failures on ext4 with Darrick's recent test
>change,
> haven't tried ceph yet.
The generic/448 test currently fails with the error codes described in
the commit log. I didn't found it useful to include in the commit
log, but here's the full test output:
File system supports the default behavior.
File system does not support unwritten extents.
File system magic#: 0xc36400
Allocation size: 4194304
18. Test file with negative SEEK_{HOLE,DATA} offsets
18.01 SEEK_HOLE expected -1 or -1, got 0. FAIL
18.02 SEEK_DATA expected -1 with errno -6, got -22. FAIL
seek sanity check failed!
Cheers,
--
Luís
WARNING: multiple messages have this Message-ID (diff)
From: Luis Henriques <lhenriques@suse.com>
To: Ilya Dryomov <idryomov@gmail.com>
Cc: "Yan\, Zheng" <zyan@redhat.com>, Sage Weil <sage@redhat.com>,
Ceph Development <ceph-devel@vger.kernel.org>,
"linux-kernel\@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] ceph: check negative offsets on ceph_llseek()
Date: Thu, 17 Aug 2017 19:40:39 +0100 [thread overview]
Message-ID: <87lgmixck8.fsf@hermes> (raw)
In-Reply-To: <CAOi1vP9RYiFuscyJqetRO3p68Bj14To5whwM6EByvtjChCk0_g@mail.gmail.com> (Ilya Dryomov's message of "Thu, 17 Aug 2017 19:57:01 +0200")
Ilya Dryomov <idryomov@gmail.com> writes:
> On Thu, Aug 17, 2017 at 3:45 PM, Luis Henriques <lhenriques@suse.com> wrote:
>> 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.
>
> It should or it does? ;)
>
Heh, it *does* make generic/448 happy.
>
> I saw generic/448 failures on ext4 with Darrick's recent test
>change,
> haven't tried ceph yet.
The generic/448 test currently fails with the error codes described in
the commit log. I didn't found it useful to include in the commit
log, but here's the full test output:
File system supports the default behavior.
File system does not support unwritten extents.
File system magic#: 0xc36400
Allocation size: 4194304
18. Test file with negative SEEK_{HOLE,DATA} offsets
18.01 SEEK_HOLE expected -1 or -1, got 0. FAIL
18.02 SEEK_DATA expected -1 with errno -6, got -22. FAIL
seek sanity check failed!
Cheers,
--
Luís
next prev parent reply other threads:[~2017-08-17 18:40 UTC|newest]
Thread overview: 7+ 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
2017-08-17 13:45 ` Luis Henriques
2017-08-17 17:57 ` Ilya Dryomov
2017-08-17 18:40 ` Luis Henriques [this message]
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=87lgmixck8.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 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.