From: Mark Brown <[email protected]>
To: Jan Kara <[email protected]>
Cc: Christian Brauner <[email protected]>,
[email protected], Christoph Hellwig <[email protected]>,
Jens Axboe <[email protected]>,
Alexander Viro <[email protected]>,
Dave Chinner <[email protected]>,
[email protected], Aishwarya TCV <[email protected]>
Subject: Re: [PATCH v2] fs: claw back a few FMODE_* bits
Date: Thu, 4 Apr 2024 12:43:30 +0100 [thread overview]
Message-ID: <[email protected]> (raw)
In-Reply-To: <20240404091215.kpphfowf5ktmouu7@quack3>
[-- Attachment #1: Type: text/plain, Size: 3914 bytes --]
On Thu, Apr 04, 2024 at 11:12:15AM +0200, Jan Kara wrote:
> On Wed 03-04-24 22:12:45, Mark Brown wrote:
> > For the past couple of days several LTP tests (open_by_handle_at0[12]
> > and name_to_handle_at01) have been failing on all the arm64 platforms
> > we're running these tests on. I ran a bisect which came back to this
> Do you have some LTP logs / kernel logs available for the failing runs?
Actually it looks like the issue went away with today's -next, but FWIW
the logging for the open_by_handle_at0[12] failures was:
tst_test.c:1690: TINFO: LTP version: 20230929
tst_test.c:1574: TINFO: Timeout per run is 0h 01m 30s
tst_buffers.c:56: TINFO: Test is using guarded buffers
name_to_handle_at01.c:94: TFAIL: open_by_handle_at() failed (0): EFAULT (14)
name_to_handle_at01.c:94: TFAIL: open_by_handle_at() failed (1): EFAULT (14)
name_to_handle_at01.c:94: TFAIL: open_by_handle_at() failed (2): EFAULT (14)
name_to_handle_at01.c:94: TFAIL: open_by_handle_at() failed (3): EFAULT (14)
name_to_handle_at01.c:94: TFAIL: open_by_handle_at() failed (4): EFAULT (14)
name_to_handle_at01.c:94: TFAIL: open_by_handle_at() failed (5): EFAULT (14)
name_to_handle_at01.c:94: TFAIL: open_by_handle_at() failed (6): EFAULT (14)
name_to_handle_at01.c:94: TFAIL: open_by_handle_at() failed (7): EFAULT (14)
name_to_handle_at01.c:94: TFAIL: open_by_handle_at() failed (8): EFAULT (14)
name_to_handle_at01.c:94: TFAIL: open_by_handle_at() failed (9): EFAULT (14)
name_to_handle_at01.c:94: TFAIL: open_by_handle_at() failed (10): EFAULT (14)
name_to_handle_at01.c:94: TFAIL: open_by_handle_at() failed (11): EFAULT (14)
name_to_handle_at01.c:94: TFAIL: open_by_handle_at() failed (12): EFAULT (14)
name_to_handle_at01.c:94: TFAIL: open_by_handle_at() failed (13): EFAULT (14)
name_to_handle_at01.c:94: TFAIL: open_by_handle_at() failed (14): EFAULT (14)
name_to_handle_at01.c:94: TFAIL: open_by_handle_at() failed (15): EFAULT (14)
name_to_handle_at01.c:94: TFAIL: open_by_handle_at() failed (16): EFAULT (14)
name_to_handle_at01.c:94: TFAIL: open_by_handle_at() failed (17): EFAULT (14)
name_to_handle_at01.c:94: TFAIL: open_by_handle_at() failed (18): EFAULT (14)
name_to_handle_at01.c:94: TFAIL: open_by_handle_at() failed (19): EFAULT (14)
name_to_handle_at01.c:94: TFAIL: open_by_handle_at() failed (20): EFAULT (14)
name_to_handle_at01.c:94: TFAIL: open_by_handle_at() failed (21): EFAULT (14)
name_to_handle_at01.c:94: TFAIL: open_by_handle_at() failed (22): EFAULT (14)
name_to_handle_at01.c:94: TFAIL: open_by_handle_at() failed (23): EFAULT (14)
name_to_handle_at01.c:94: TFAIL: open_by_handle_at() failed (24): EFAULT (14)
name_to_handle_at01.c:94: TFAIL: open_by_handle_at() failed (25): EFAULT (14)
name_to_handle_at01.c:94: TFAIL: open_by_handle_at() failed (26): EFAULT (14)
Summary:
passed 0
failed 27
broken 0
skipped 0
warnings 0
tst_test.c:1690: TINFO: LTP version: 20230929
tst_test.c:1574: TINFO: Timeout per run is 0h 01m 30s
tst_buffers.c:56: TINFO: Test is using guarded buffers
open_by_handle_at02.c:92: TFAIL: invalid-dfd: open_by_handle_at() should fail with EBADF: EFAULT (14)
open_by_handle_at02.c:92: TFAIL: stale-dfd: open_by_handle_at() should fail with ESTALE: EFAULT (14)
open_by_handle_at02.c:98: TPASS: invalid-file-handle: open_by_handle_at() failed as expected: EFAULT (14)
open_by_handle_at02.c:98: TPASS: high-file-handle-size: open_by_handle_at() failed as expected: EINVAL (22)
open_by_handle_at02.c:98: TPASS: zero-file-handle-size: open_by_handle_at() failed as expected: EINVAL (22)
tst_capability.c:29: TINFO: Dropping CAP_DAC_READ_SEARCH(2)
tst_capability.c:41: TINFO: Permitting CAP_DAC_READ_SEARCH(2)
open_by_handle_at02.c:98: TPASS: no-capability: open_by_handle_at() failed as expected: EPERM (1)
open_by_handle_at02.c:92: TFAIL: symlink: open_by_handle_at() should fail with ELOOP: EFAULT (14)
Summary:
passed 4
failed 3
broken 0
skipped 0
warnings 0
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2024-04-04 11:43 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-28 12:27 [PATCH v2] fs: claw back a few FMODE_* bits Christian Brauner
2024-03-28 13:08 ` Christoph Hellwig
2024-04-02 10:51 ` Jan Kara
2024-04-02 12:59 ` Jens Axboe
2024-04-03 21:12 ` Mark Brown
2024-04-04 9:12 ` Jan Kara
2024-04-04 11:43 ` Mark Brown [this message]
2024-04-05 10:27 ` Christian Brauner
2024-04-05 11:12 ` Mark Brown
2024-04-04 0:18 ` Al Viro
2024-04-05 10:06 ` Christian Brauner
2024-04-06 6:10 ` Al Viro
2024-04-06 6:16 ` Al Viro
2024-04-09 9:12 ` Christian Brauner
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 \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
/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