a) Please don't just change the verification tags without showing what
testing has been performed. I'm moving the tags back to verification-
needed.

From the SRU acceptance message:
"""
If this package fixes the bug for you, please add a comment to this bug, 
mentioning the version of the package you tested, what testing has been 
performed on the package and change the tag from verification-needed-noble to 
verification-done-noble.
"""

b) There are two facts about this bug. From the description:
b1) dbus-broker in noble, oracular and plucky only checks for EINVAL when 
calling the SO_PEERPIDFD getsockopt to check if a process already exited
b2) The kernel in 6.16 is changing the return value from EINVAL to ESRCH

So to reproduce the bug, or show that it is fixed, we need to trigger
the mentioned getsockopt() call, *AND* do that under kernel 6.16.

The test plan also asks for a container, but without specifying the
host. In containers, the running kernel is that one from the host, and
since this bug is about a kernel interaction, I would think this to be
an important detail.

Overall, I think the test plan is not covering what's needed, nor
demonstrating that the bug is fixed. I don't know if we have a 6.16
kernel available for testing yet.

Could someone please clarify these issues? But at the very least, this
cannot be released now because the test plan verification doesn't even
have a comment stating what was done.

** Tags removed: verification-done verification-done-noble 
verification-done-oracular verification-done-plucky
** Tags added: verification-needed verification-needed-noble 
verification-needed-oracular verification-needed-plucky

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2110040

Title:
  dbus-broker: fix compatibility with newer kernel's error code for
  SO_PEERPIDFD error case

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dbus-broker/+bug/2110040/+subscriptions


-- 
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to