All of lore.kernel.org
 help / color / mirror / Atom feed
From: Petr Vorel <pvorel@suse.cz>
To: Anders Roxell <anders.roxell@linaro.org>,
	Martin Doucha <martin.doucha@suse.com>,
	ltp@lists.linux.it
Subject: Re: [LTP] [PATCH] accept02: Join the multicast group on lo
Date: Wed, 30 Sep 2026 16:10:54 +0200	[thread overview]
Message-ID: <20260930141054.GC2721643@pevik> (raw)
In-Reply-To: <20260930125347.GB2652589@pevik>

> Hi Anders, all,

> > The test joins the multicast group with interface 0. Then the kernel
> > needs a route to 224.0.0.0 to find a device. When we only have lo,
> > like in a QEMU guest with no network, there is no such route and the
> > test breaks:

> >   accept02.c:52: TBROK: setsockopt(3, 0, 42, ...) failed: ENODEV (19)

> > All traffic in the test goes over 127.0.0.1, so join the group on lo.

> > Signed-off-by: Anders Roxell <anders.roxell@linaro.org>
> > ---
> >  testcases/kernel/syscalls/accept/accept02.c | 3 ++-
> >  1 file changed, 2 insertions(+), 1 deletion(-)

> > diff --git a/testcases/kernel/syscalls/accept/accept02.c b/testcases/kernel/syscalls/accept/accept02.c
> > index 17056625e933..09a1c35e2591 100644
> > --- a/testcases/kernel/syscalls/accept/accept02.c
> > +++ b/testcases/kernel/syscalls/accept/accept02.c
> > @@ -22,6 +22,7 @@
> >  #include <errno.h>
> >  #include <sys/socket.h>
> >  #include "tst_test.h"
> > +#include "tst_netdevice.h"
> >  #include "tst_safe_net.h"
> >  #include "tst_safe_pthread.h"

> > @@ -112,7 +113,7 @@ static void setup(void)
> >  	client_addr = tst_alloc(sizeof(*client_addr));
> >  	mc_group = tst_alloc(sizeof(*mc_group));

> > -	mc_group->gr_interface = 0;
> > +	mc_group->gr_interface = NETDEV_INDEX_BY_NAME("lo");

> Reviewed-by: Petr Vorel <pvorel@suse.cz>

> I tested that it really fixes the problem when no network and runs ok.
> But I'm not 100% sure that it did not affect the CVE reproducibility.
> Therefore I do not add my TBT.

And unfortunately this should be really verified if the change does not affect
reproducibility. Hopefully Martin will get time for that soon, but this will for
sure will not make it into the release planned for today.

Kind regards,
Petr

> Kind regards,
> Petr

-- 
Mailing list info: https://lists.linux.it/listinfo/ltp

  reply	other threads:[~2026-09-30 14:11 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-28 21:27 [LTP] [PATCH] accept02: Join the multicast group on lo Anders Roxell
2026-09-28 23:50 ` [LTP] " linuxtestproject.agent
2026-09-30 12:53 ` [LTP] [PATCH] " Petr Vorel
2026-09-30 14:10   ` Petr Vorel [this message]
2026-09-30 14:19 ` Martin Doucha
2026-09-30 14:28   ` Petr Vorel

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=20260930141054.GC2721643@pevik \
    --to=pvorel@suse.cz \
    --cc=anders.roxell@linaro.org \
    --cc=ltp@lists.linux.it \
    --cc=martin.doucha@suse.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.