From: Bruce Dubbs <bruce.dubbs@gmail.com>
To: Karel Zak <kzak@redhat.com>,
linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org,
util-linux@vger.kernel.org
Cc: "Douglas R. Reno" <renodr2002@gmail.com>
Subject: Re: [ANNOUNCE] util-linux v2.39
Date: Thu, 18 May 2023 18:31:47 -0500 [thread overview]
Message-ID: <652d32c5-4b33-ce3a-3de7-9ebc064bbdcb@gmail.com> (raw)
In-Reply-To: <20230517112242.3rubpxvxhzsc4kt2@ws.net.home>
On 5/17/23 06:22, Karel Zak wrote:
>
> The util-linux release v2.39 is available at
>
> http://www.kernel.org/pub/linux/utils/util-linux/v2.39
>
> Feedback and bug reports, as always, are welcomed.
Karel, I have installed util-linux v2.39 in LFS and have run into a problem with one
test, test_mkfds. Actually the test passes, but does not clean up after itself.
What is left over is:
tester 32245 1 0 15:43 ? 00:00:00 /sources/util-linux-2.39/test_mkfds
-q udp 3 4 server-port=34567 client-port=23456 server-do-bind=1 client-do-bind=1
client-do-connect=1
tester 32247 1 0 15:43 ? 00:00:00 /sources/util-linux-2.39/test_mkfds
-q udp6 3 4 lite=1 server-port=34567 client-port=23456 server-do-bind=1
client-do-bind=1 client-do-connect=1
It's possible it may be due to something we are doing inside our chroot environment,
but we've not had this type of problem with earlier versions of util-linux.
In all I do have:
All 261 tests PASSED
but the left over processes interfere later when we try to remove the non-root user,
tester, that runs the tests. I can work around the problem by disabling test_mkfds,
but thought you would like to know.
-- Bruce
next prev parent reply other threads:[~2023-05-18 23:31 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-17 11:22 [ANNOUNCE] util-linux v2.39 Karel Zak
2023-05-17 13:48 ` Christian Brauner
2023-05-18 10:23 ` Karel Zak
2023-05-18 14:00 ` Christian Brauner
2023-05-18 23:31 ` Bruce Dubbs [this message]
2023-05-18 23:42 ` Masatake YAMATO
2023-05-19 22:43 ` Masatake YAMATO
2023-05-19 22:56 ` Bruce Dubbs
2023-05-20 23:16 ` Bruce Dubbs
2023-05-21 21:48 ` Masatake YAMATO
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=652d32c5-4b33-ce3a-3de7-9ebc064bbdcb@gmail.com \
--to=bruce.dubbs@gmail.com \
--cc=kzak@redhat.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=renodr2002@gmail.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).