From: Mirsad Todorovac <mirsad.todorovac@alu.unizg.hr>
To: Kuniyuki Iwashima <kuniyu@amazon.com>
Cc: alexander@mihalicyn.com, davem@davemloft.net,
edumazet@google.com, fw@strlen.de, kuba@kernel.org,
linux-kernel@vger.kernel.org, linux-kselftest@vger.kernel.org,
netdev@vger.kernel.org, pabeni@redhat.com, shuah@kernel.org
Subject: Re: selftests: net/af_unix test_unix_oob [FAILED]
Date: Tue, 8 Aug 2023 01:09:03 +0200 [thread overview]
Message-ID: <ba4da366-b8cf-ca36-e2dc-cce7260cccf8@alu.unizg.hr> (raw)
In-Reply-To: <20230807204648.50070-1-kuniyu@amazon.com>
On 8/7/23 22:46, Kuniyuki Iwashima wrote:
> From: Mirsad Todorovac <mirsad.todorovac@alu.unizg.hr>
> Date: Mon, 7 Aug 2023 21:44:41 +0200
>> Hi all,
>>
>> In the kernel 6.5-rc5 build on Ubuntu 22.04 LTS (jammy jellyfish) on a Ryzen 7950 assembled box,
>> vanilla torvalds tree kernel, the test test_unix_oob unexpectedly fails:
>>
>> # selftests: net/af_unix: test_unix_oob
>> # Test 2 failed, sigurg 23 len 63 OOB %
>>
>> It is this code:
>>
>> /* Test 2:
>> * Verify that the first OOB is over written by
>> * the 2nd one and the first OOB is returned as
>> * part of the read, and sigurg is received.
>> */
>> wait_for_data(pfd, POLLIN | POLLPRI);
>> len = 0;
>> while (len < 70)
>> len = recv(pfd, buf, 1024, MSG_PEEK);
>> len = read_data(pfd, buf, 1024);
>> read_oob(pfd, &oob);
>> if (!signal_recvd || len != 127 || oob != '#') {
>> fprintf(stderr, "Test 2 failed, sigurg %d len %d OOB %c\n",
>> signal_recvd, len, oob);
>> die(1);
>> }
>>
>> In 6.5-rc4, this test was OK, so it might mean we have a regression?
>
> Thanks for reporting.
>
> I confirmed the test doesn't fail on net-next at least, but it's based
> on v6.5-rc4.
>
> ---8<---
> [root@localhost ~]# ./test_unix_oob
> [root@localhost ~]# echo $?
> 0
> [root@localhost ~]# uname -r
> 6.5.0-rc4-01192-g66244337512f
> ---8<---
>
> I'll check 6.5-rc5 later.
Hi, Kuniyuki,
It seems that there is a new development. I could reproduce the error with the failed test 2
as early as 6.0-rc1. However, the gotcha is that the error appears to be sporadically manifested
(possibly a race)?
I am currently attempting a bisect.
Kind regards,
Mirsad
>> marvin@defiant:~/linux/kernel/linux_torvalds$ grep test_unix_oob ../kselftest-6.5-rc4-1.log
>> /net/af_unix/test_unix_oob
>> # selftests: net/af_unix: test_unix_oob
>> ok 2 selftests: net/af_unix: test_unix_oob
>> marvin@defiant:~/linux/kernel/linux_torvalds$
>>
>> Hope this helps.
>>
>> NOTE: the kernel is vanilla torvalds tree, only "dirty" because the selftests were modified.
>>
>> Kind regards,
>> Mirsad Todorovac
next prev parent reply other threads:[~2023-08-07 23:12 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-07 19:44 Mirsad Todorovac
2023-08-07 20:46 ` Kuniyuki Iwashima
2023-08-07 23:09 ` Mirsad Todorovac [this message]
2023-08-08 8:53 ` Mirsad Todorovac
2023-08-14 8:54 ` Mirsad Todorovac
2023-08-20 10:34 ` selftests: net/af_unix test_unix_oob [FAILED][NEW] Mirsad Todorovac
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=ba4da366-b8cf-ca36-e2dc-cce7260cccf8@alu.unizg.hr \
--to=mirsad.todorovac@alu.unizg.hr \
--cc=alexander@mihalicyn.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=fw@strlen.de \
--cc=kuba@kernel.org \
--cc=kuniyu@amazon.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=shuah@kernel.org \
/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®