mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Arnd Bergmann" <arnd@arndb.de>
To: "Naresh Kamboju" <naresh.kamboju@linaro.org>,
	"open list" <linux-kernel@vger.kernel.org>,
	"LTP List" <ltp@lists.linux.it>,
	lkft-triage@lists.linaro.org,
	"Linux Regressions" <regressions@lists.linux.dev>,
	"Christian Brauner" <brauner@kernel.org>
Cc: "Dan Carpenter" <dan.carpenter@linaro.org>,
	"Anders Roxell" <anders.roxell@linaro.org>,
	"Benjamin Copeland" <benjamin.copeland@linaro.org>,
	chrubis <chrubis@suse.cz>
Subject: Re: next-20241203: LTP syscalls: name_to_handle_at01 and open_by_handle_at01 failed
Date: Wed, 04 Dec 2024 10:45:21 +0100	[thread overview]
Message-ID: <0b91d70b-bc7a-462c-a52d-092df1f91e39@app.fastmail.com> (raw)
In-Reply-To: <CA+G9fYv4tUvUj1+rv5AU98QT9P8-RYVTkLAc-fCbLvy3wLtpJw@mail.gmail.com>

On Wed, Dec 4, 2024, at 10:38, Naresh Kamboju wrote:
> The following LTP syscalls name_to_handle_at01 and open_by_handle_at01
> / 02 tests
> failed on the Linux next-20241203 tag.
>
> First seen on Linux next-20241204 tag
> GOOD: Linux next-20241128 tag
> BAD: Linux next-20241203 tag

I see Christian Brauner's pidfs series getting merged between
those tags:

06b93f9cebca selftests/pidfd: add pidfs file handle selftests
c605dbc9850c pidfs: check for valid ioctl commands
fa3364a34c29 Merge patch series "pidfs: implement file handle support"
b3b0ad5f7eb3 pidfs: implement file handle support
6bf89dd80121 exportfs: add permission method
3fa98a43cb09 fhandle: pull CAP_DAC_READ_SEARCH check into may_decode_fh()
4afd8ca9c4b4 exportfs: add open method
e911ec82c48d fhandle: simplify error handling
a5eeba41d048 Merge patch series "pidfs: file handle preliminaries"
1010ba2fe904 pidfs: support FS_IOC_GETVERSION
5fe02e1e8f8c pidfs: remove 32bit inode number handling
799a5aeedc0d pidfs: rework inode number allocation
5dc3727ebd0b Merge patch series "exportfs: add flag to allow marking export operations as only supporting file handles"
4309a6099bfd ovl: restrict to exportable file handles
5e28f4a9d373 kernfs: restrict to local file handles
29b35e260929 exportfs: add flag to indicate local file handles

Adding Christian to Cc, he probably already knows what is
going on, and if this is a regression in the kernel or a
problem in the LTP test case.

    Arnd

> List of device :
>   - juno-r2 - arm64
>   - juno-r2-compat
>   - qemu-arm64
>   - qemu-arm64-compat
>   - qemu-armv7
>   - qemu-riscv64
>   - qemu-x86_64
>   - qemu-x86_64-compat
>   - x15 - arm
>   - x86_64
>   - x86-compat
>
> ltp-syscalls:
>     * open_by_handle_at01
>     * open_by_handle_at02
>     * name_to_handle_at01
>
> Reported-by: Linux Kernel Functional Testing <lkft@linaro.org>
>
> Test failed log:
> =================
> tst_buffers.c:57: TINFO: Test is using guarded buffers
> name_to_handle_at01.c:102: TPASS: name_to_handle_at() passed (0)
> name_to_handle_at01.c:98: TBROK: fstat(1,0x7fffda449ce0) failed: EBADF (9)
>
> Summary:
> passed   1
> failed   0
> broken   1
>
> tst_tmpdir.c:316: TINFO: Using /scratch/ltp-B0Mf6pVtaR/LTP_opehXJa6X
> as tmpdir (ext2/ext3/ext4 filesystem)
> tst_test.c:1860: TINFO: LTP version: 20240930
> tst_test.c:1864: TINFO: Tested kernel: 6.13.0-rc1-next-20241203 #1 SMP
> PREEMPT_DYNAMIC @1733269464 x86_64
> tst_test.c:1703: TINFO: Timeout per run is 0h 02m 30s
> tst_buffers.c:57: TINFO: Test is using guarded buffers
> open_by_handle_at01.c:101: TPASS: open_by_handle_at() passed (0)
> open_by_handle_at01.c:97: TBROK: fstat(1,0x7fff409f94e0) failed: EBADF (9)
>
> Summary:
> passed   1
> failed   0
> broken   1
> skipped  0
> warnings 0
> tst_tmpdir.c:316: TINFO: Using /scratch/ltp-B0Mf6pVtaR/LTP_opeN4blFw
> as tmpdir (ext2/ext3/ext4 filesystem)
> tst_test.c:1860: TINFO: LTP version: 20240930
> tst_test.c:1864: TINFO: Tested kernel: 6.13.0-rc1-next-20241203 #1 SMP
> PREEMPT_DYNAMIC @1733269464 x86_64
> tst_test.c:1703: TINFO: Timeout per run is 0h 02m 30s
> tst_buffers.c:57: TINFO: Test is using guarded buffers
> open_by_handle_at02.c:98: TPASS: invalid-dfd: open_by_handle_at()
> failed as expected: EBADF (9)
> open_by_handle_at02.c:86: TFAIL: stale-dfd: open_by_handle_at() passed
> unexpectedly
> open_by_handle_at02.c:85: TBROK: close(1) failed: EBADF (9)
>
> Summary:
> passed   1
> failed   1
>
> Links:
> ---
> - 
> https://storage.tuxsuite.com/public/linaro/lkft/builds/2pjAOWmHmfmcNEt4XL6h7GdVCZf/
> - 
> https://qa-reports.linaro.org/lkft/linux-next-master/build/next-20241203/testrun/26192368/suite/ltp-syscalls/tests/
> - 
> https://qa-reports.linaro.org/lkft/linux-next-master/build/next-20241203/testrun/26192368/suite/ltp-syscalls/test/name_to_handle_at01/log
> - 
> https://qa-reports.linaro.org/lkft/linux-next-master/build/next-20241203/testrun/26192368/suite/ltp-syscalls/test/name_to_handle_at01/details/
> - 
> https://qa-reports.linaro.org/lkft/linux-next-master/build/next-20241203/testrun/26188858/suite/ltp-syscalls/test/open_by_handle_at02/history/
>
> Steps to reproduce:
> ------------
> - tuxmake \
>         --runtime podman \
>         --target-arch arm64 \
>         --toolchain gcc-13 \
>         --kconfig
> https://storage.tuxsuite.com/public/linaro/lkft/builds/2pjAOWmHmfmcNEt4XL6h7GdVCZf/config
>
> metadata:
> ----
>   git describe: 6.13.0-rc1-next-20241203
>   git repo: 
> https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git
>   git sha: c245a7a79602ccbee780c004c1e4abcda66aec32
>   kernel config:
> https://storage.tuxsuite.com/public/linaro/lkft/builds/2pjAOWmHmfmcNEt4XL6h7GdVCZf/config
>   build url: 
> https://storage.tuxsuite.com/public/linaro/lkft/builds/2pjAOWmHmfmcNEt4XL6h7GdVCZf/
>   toolchain: gcc-13
>   config: gcc-13-defconfig-lkftconfig
>   arch: arm64
>
> --
> Linaro LKFT
> https://lkft.linaro.org

      reply	other threads:[~2024-12-04  9:45 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-12-04  9:38 Naresh Kamboju
2024-12-04  9:45 ` Arnd Bergmann [this message]

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=0b91d70b-bc7a-462c-a52d-092df1f91e39@app.fastmail.com \
    --to=arnd@arndb.de \
    --cc=anders.roxell@linaro.org \
    --cc=benjamin.copeland@linaro.org \
    --cc=brauner@kernel.org \
    --cc=chrubis@suse.cz \
    --cc=dan.carpenter@linaro.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lkft-triage@lists.linaro.org \
    --cc=ltp@lists.linux.it \
    --cc=naresh.kamboju@linaro.org \
    --cc=regressions@lists.linux.dev \
    /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

all inboxes | Powered by JetHome®