mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Benjamin Drung <bdrung@debian.org>
To: linux-kernel@vger.kernel.org
Subject: Heisenbug: no DHCP packets received by dnsmasq (dracut-ng test suite)
Date: Thu, 05 Mar 2026 16:33:52 +0100	[thread overview]
Message-ID: <b7b5506f25868e9739ae5b282b39611730cfa4bd.camel@debian.org> (raw)

Hi everyone,

I ran into a heisenbug where the culprit is not clear to me. It could be
the linux kernel, QEMU, or dnsmasq. We want to switch from
isc-dhcp-server to dnsmasq in the dracut-ng test suite. I prepared this
change in https://github.com/dracut-ng/dracut-ng/pull/2271 but test 60
fails on most distribution.

How to reproduce
================

Clone dracut-ng and include the dnsmasq patch from
https://github.com/dracut-ng/dracut-ng/pull/2271
Then run `test/test.sh debian:sid 60`. You can replace `debian:sid` by
other containers.

On all containers tested so far (Fedora, Debian, OpenSUSE, etc) except
for the Ubuntu containers the dracut-ng test 60 fails. See
https://github.com/dracut-ng/dracut-ng/issues/2283 for the tested
containers.

Test 60 setup
=============

In a podman container start a QEMU VM with "-netdev socket" or
"-netdev dgram" as server. This server runs dnsmasq. The test has
multiple client tests. Each client test start a QEMU VM as client
connecting the netdev to the server. The same server is used for all
client tests. The client will try to get a DHCP lease from dnsmasq.

Heisenbug symptoms
==================

The third (when using "-netdev socket") or the fifth (when using 
"-netdev dgram") client test hangs. The client sends DHCP discover
packets but dnsmasq on the server never receives them.

When I start to debug this behavior by running tcpdump on the server,
the DHCP discover packets are reaching dnsmasq and the test succeeds.

Running only the failing client test will make the client test succeed.

Dracut-ng bug: https://github.com/dracut-ng/dracut-ng/issues/2283

-- 
Benjamin Drung
Debian & Ubuntu Developer

                 reply	other threads:[~2026-03-05 15:33 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=b7b5506f25868e9739ae5b282b39611730cfa4bd.camel@debian.org \
    --to=bdrung@debian.org \
    --cc=linux-kernel@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

all inboxes | Powered by JetHome®