util-linux.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Bruce Dubbs <bruce.dubbs@gmail.com>
To: Karel Zak <kzak@redhat.com>
Cc: Util-Linux <util-linux@vger.kernel.org>
Subject: Re: util-linux-2.35.2 test failures
Date: Wed, 27 May 2020 13:07:09 -0500	[thread overview]
Message-ID: <99d36043-9806-bd95-0630-7a920e8476d4@gmail.com> (raw)
In-Reply-To: <d8616084-1e16-abc2-d0d6-834073d96fca@gmail.com>

On 5/27/20 10:55 AM, Bruce Dubbs wrote:
> On 5/27/20 8:11 AM, Karel Zak wrote:
>> On Tue, May 26, 2020 at 05:34:13PM -0500, Bruce Dubbs wrote:
>>> I'm getting three test failures and hope I can get someone to help.
>>>
>>> The test failures are  ipcs/mk-rm-msg, ipcs/mk-rm-sem, and 
>>> ipcs/mk-rm-shm.
>>>
>>> Concentrating on mk-rm-msg, I found on the system:
>>>
>>> ./tests/output/ipcs/mk-rm-msg
>>> ./tests/ts/ipcs/mk-rm-msg
>>> ./tests/expected/ipcs/mk-rm-msg
>>>
>>> The contents of the output and the expected files are identical:
>>>
>>> Message queue id: <was_number>
>>> 1
>>> Message queue id: <was_number>
>>>
>>> I am running the tests as a non-privileged user.
>>>
>>> If I run the commands:
>>>
>>> $ ipcmk -Q  (returns 24)
>>> $ ipcs -q -i 24
>>> $ ipcrm -q 24
>>> $ echo $?
>>> 0
>>>
>>> Everything looks OK.  Does anyone have an idea why this test (these 
>>> tests)
>>> are failing?
>>
>> I had no time to play with it yet, but according to feedback from
>> https://github.com/karelzak/util-linux/issues/1042 there is some kernel
>> regression:
>>
>>   The ipcs tests are failing due to a regression in kernels 5.6.8
>>   through 5.6.13. Or mainline commits between
>>   89163f93c6f969da5811af5377cc10173583123b and
>>   5e698222c70257d13ae0816720dde57c56f81e15 (apparently including your
>>   5.7.0-rc0).
> 
> Thanks.  I'll try 5.6.14 and report back.

Indeed updating to kernel 5.6.14 fixed the ipcs test issues.  Thanks for 
the help.

Additionally I'd like to report one minor warning when building with gcc10:

login-utils/logindefs.c: In function ‘get_hushlogin_status’:
login-utils/logindefs.c:370:20: warning: ‘%s’ directive writing likely 
15 or more bytes into a region of size between 9 and 8191 
[-Wformat-overflow=]
   370 |   sprintf(buf, "%s/%s", pwd->pw_dir, file);
       |                    ^~
login-utils/logindefs.c:370:16: note: assuming directive output of 15 bytes
   370 |   sprintf(buf, "%s/%s", pwd->pw_dir, file);
       |                ^~~~~~~
login-utils/logindefs.c:370:3: note: ‘sprintf’ output 2 or more bytes 
(assuming 8199) into a destination of size 8192
   370 |   sprintf(buf, "%s/%s", pwd->pw_dir, file);
       |   ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

   -- Bruce

      reply	other threads:[~2020-05-27 18:07 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-26 22:34 util-linux-2.35.2 test failures Bruce Dubbs
2020-05-26 23:07 ` Aurélien Lajoie
2020-05-26 23:36   ` Bruce Dubbs
2020-05-27  3:11     ` Aurélien Lajoie
2020-05-27  3:43       ` Bruce Dubbs
2020-05-27  5:13         ` Bruce Dubbs
2020-05-27 13:11 ` Karel Zak
2020-05-27 15:55   ` Bruce Dubbs
2020-05-27 18:07     ` Bruce Dubbs [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=99d36043-9806-bd95-0630-7a920e8476d4@gmail.com \
    --to=bruce.dubbs@gmail.com \
    --cc=kzak@redhat.com \
    --cc=util-linux@vger.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;
as well as URLs for NNTP newsgroup(s).