From: Jan Stancek <jstancek@redhat.com>
To: Christoph Hellwig <hch@infradead.org>
Cc: "Darrick J. Wong" <darrick.wong@oracle.com>,
Naresh Kamboju <naresh.kamboju@linaro.org>,
LTP List <ltp@lists.linux.it>,
Linux-Next Mailing List <linux-next@vger.kernel.org>,
linux-fsdevel@vger.kernel.org, chrubis <chrubis@suse.cz>,
open list <linux-kernel@vger.kernel.org>,
Al Viro <viro@zeniv.linux.org.uk>,
Mark Brown <broonie@kernel.org>, Arnd Bergmann <arnd@arndb.de>,
lkft-triage@lists.linaro.org,
linux-ext4 <linux-ext4@vger.kernel.org>,
Theodore Ts'o <tytso@mit.edu>
Subject: Re: LTP: diotest4.c:476: read to read-only space. returns 0: Success
Date: Mon, 11 Nov 2019 05:38:54 -0500 (EST) [thread overview]
Message-ID: <1757087132.11450258.1573468734360.JavaMail.zimbra@redhat.com> (raw)
In-Reply-To: <20191111083815.GA29540@infradead.org>
----- Original Message -----
> Is this a new test?
No, it's not new.
> If not why was this never reported? Sounds like
> we should add this test case to xfstests.
I'm guessing not that many users still run 32bit kernels.
Naresh' setup is using ext4, so I assume he noticed only
after recent changes in linux-next wrt. directio and ext4.
Regards,
Jan
WARNING: multiple messages have this Message-ID (diff)
From: Jan Stancek <jstancek@redhat.com>
To: ltp@lists.linux.it
Subject: [LTP] LTP: diotest4.c:476: read to read-only space. returns 0: Success
Date: Mon, 11 Nov 2019 05:38:54 -0500 (EST) [thread overview]
Message-ID: <1757087132.11450258.1573468734360.JavaMail.zimbra@redhat.com> (raw)
In-Reply-To: <20191111083815.GA29540@infradead.org>
----- Original Message -----
> Is this a new test?
No, it's not new.
> If not why was this never reported? Sounds like
> we should add this test case to xfstests.
I'm guessing not that many users still run 32bit kernels.
Naresh' setup is using ext4, so I assume he noticed only
after recent changes in linux-next wrt. directio and ext4.
Regards,
Jan
next prev parent reply other threads:[~2019-11-11 10:39 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-07 13:59 LTP: diotest4.c:476: read to read-only space. returns 0: Success Naresh Kamboju
2019-11-07 13:59 ` [LTP] " Naresh Kamboju
2019-11-08 0:20 ` Jan Stancek
2019-11-08 0:20 ` [LTP] " Jan Stancek
2019-11-11 1:26 ` Darrick J. Wong
2019-11-11 1:26 ` [LTP] " Darrick J. Wong
2019-11-11 8:19 ` Jan Stancek
2019-11-11 8:19 ` [LTP] " Jan Stancek
2019-11-11 8:38 ` Christoph Hellwig
2019-11-11 8:38 ` [LTP] " Christoph Hellwig
2019-11-11 10:28 ` [PATCH] iomap: fix return value of iomap_dio_bio_actor on 32bit systems Jan Stancek
2019-11-11 10:28 ` [LTP] " Jan Stancek
2019-11-11 10:36 ` Christoph Hellwig
2019-11-11 10:36 ` [LTP] " Christoph Hellwig
2019-11-12 1:24 ` Darrick J. Wong
2019-11-12 1:24 ` [LTP] " Darrick J. Wong
2019-11-11 10:38 ` Jan Stancek [this message]
2019-11-11 10:38 ` [LTP] LTP: diotest4.c:476: read to read-only space. returns 0: Success Jan Stancek
2019-11-11 18:26 ` Naresh Kamboju
2019-11-11 18:26 ` [LTP] " Naresh Kamboju
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=1757087132.11450258.1573468734360.JavaMail.zimbra@redhat.com \
--to=jstancek@redhat.com \
--cc=arnd@arndb.de \
--cc=broonie@kernel.org \
--cc=chrubis@suse.cz \
--cc=darrick.wong@oracle.com \
--cc=hch@infradead.org \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=lkft-triage@lists.linaro.org \
--cc=ltp@lists.linux.it \
--cc=naresh.kamboju@linaro.org \
--cc=tytso@mit.edu \
--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 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.