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,
"Liam R. Howlett" <Liam.Howlett@Oracle.com>,
"Andrew Morton" <akpm@linux-foundation.org>
Cc: chrubis <chrubis@suse.cz>, "Shakeel Butt" <shakeelb@google.com>,
"Greg Kroah-Hartman" <gregkh@linuxfoundation.org>,
"Vasily Averin" <vvs@virtuozzo.com>,
"Luiz Capitulino" <luizcap@amazon.com>
Subject: Re: next-20230124: LTP: shmctl01.c:120: TFAIL: after child shmdt() shm_nattcg=20 expected 0
Date: Wed, 25 Jan 2023 16:23:24 +0100 [thread overview]
Message-ID: <777c2c8f-1d2a-48d4-a662-38a87341e92c@app.fastmail.com> (raw)
In-Reply-To: <CA+G9fYsoGiJRYeuUpak+5aQ4Ev8s_u0YZKXMQuP7CwQsWo1G6g@mail.gmail.com>
On Wed, Jan 25, 2023, at 16:11, Naresh Kamboju wrote:
> LTP syscalls shmctl01 test failed on Linux next-20230124 tag across all the
> available architectures with following error logs,
>
> tst_test.c:1524: TINFO: Timeout per run is 0h 05m 00s
> shmctl01.c:256: TINFO: shm_id=9 maps to kernel index=9
> shmctl01.c:220: TINFO: Basic checks
> shmctl01.c:175: TPASS: IPC_STAT: shm_segsz=2048
> shmctl01.c:182: TPASS: IPC_STAT: shm_cpid=103946
> shmctl01.c:189: TPASS: IPC_STAT: shm_ctime=1674621556 in range
> <1674621556,1674621556>
> shmctl01.c:175: TPASS: SHM_STAT: shm_segsz=2048
> shmctl01.c:182: TPASS: SHM_STAT: shm_cpid=103946
> shmctl01.c:189: TPASS: SHM_STAT: shm_ctime=1674621556 in range
> <1674621556,1674621556>
> shmctl01.c:220: TINFO: Children attach SHM
> shmctl01.c:116: TPASS: before child shmat() shm_nattch=0
> shmctl01.c:116: TPASS: after child shmat() shm_nattch=20
> shmctl01.c:120: TFAIL: after child shmdt() shm_nattcg=20 expected 0
> shmctl01.c:220: TINFO: Chidlren inherit SHM
> shmctl01.c:116: TPASS: inherited after fork() shm_nattch=21
> shmctl01.c:120: TFAIL: after child shmdt() shm_nattcg=21 expected 1
> shmctl01.c:120: TFAIL: after parent shmdt() shm_nattcg=21 expected 0
>
> Reported-by: Linux Kernel Functional Testing <lkft@linaro.org>
>
$ git log ..next-20230125 --stat --stat ipc/
commit 823fb3d78226e9b89c6a707654bd3284b06aef61
Author: Liam R. Howlett <Liam.Howlett@Oracle.com>
Date: Fri Jan 20 11:26:16 2023 -0500
ipc/shm: use the vma iterator for munmap calls
Pass through the vma iterator to do_vmi_munmap() to handle the iterator
state internally
Link: https://lkml.kernel.org/r/20230120162650.984577-16-Liam.Howlett@oracle.com
Signed-off-by: Liam R. Howlett <Liam.Howlett@oracle.com>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
ipc/shm.c | 11 +++++------
1 file changed, 5 insertions(+), 6 deletions(-)
Sven Schnelle also reported this earlier today:
https://lore.kernel.org/all/20230125134558.mm3dopfa7cxqux5h@revolver/
Arnd
> Test logs:
> https://qa-reports.linaro.org/lkft/linux-next-master/build/next-20230124/testrun/14344836/suite/ltp-syscalls/test/shmat01/details/
> https://qa-reports.linaro.org/lkft/linux-next-master/build/next-20230125/testrun/14356742/suite/ltp-syscalls/test/shmat01/log
>
> Test history:
> https://qa-reports.linaro.org/lkft/linux-next-master/build/next-20230125/testrun/14356742/suite/ltp-syscalls/test/shmat01/history/
>
> metadata:
> git_ref: master
> git_repo: https://gitlab.com/Linaro/lkft/mirrors/next/linux-next
> git_sha: a54df7622717a40ddec95fd98086aff8ba7839a6
> git_describe: next-20230124
> kernel_version: 6.2.0-rc5
> kernel-config:
> https://storage.tuxsuite.com/public/linaro/lkft/builds/2Kl19cvIBraXOcZpBGCPzCajGAs/config
> build-url:
> https://gitlab.com/Linaro/lkft/mirrors/next/linux-next/-/pipelines/755587911
> artifact-location:
> https://storage.tuxsuite.com/public/linaro/lkft/builds/2Kl19cvIBraXOcZpBGCPzCajGAs/
> toolchain: gcc-11
>
> --
> Linaro LKFT
> https://lkft.linaro.org
prev parent reply other threads:[~2023-01-25 15:23 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-25 15:11 Naresh Kamboju
2023-01-25 15:23 ` 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=777c2c8f-1d2a-48d4-a662-38a87341e92c@app.fastmail.com \
--to=arnd@arndb.de \
--cc=Liam.Howlett@Oracle.com \
--cc=akpm@linux-foundation.org \
--cc=chrubis@suse.cz \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lkft-triage@lists.linaro.org \
--cc=ltp@lists.linux.it \
--cc=luizcap@amazon.com \
--cc=naresh.kamboju@linaro.org \
--cc=shakeelb@google.com \
--cc=vvs@virtuozzo.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
all inboxes | Powered by JetHome®