netdev - Re: Bug#1103242: /bin/ip: "ip mon" does not exit when output is gone

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [day] [month] [year] [list]

Message-ID: <CAMw=ZnSZZgjN3asWLO9BvHTXDeiAf=Peo23sSvZRQbds3vWP=w@mail.gmail.com>
Date: Wed, 16 Apr 2025 11:34:12 +0100
From: Luca Boccassi <bluca@...ian.org>
To: David Ahern <dsahern@...il.com>, Stephen Hemminger <stephen@...workplumber.org>
Cc: 1103242@...s.debian.org, Simon Richter <sjr@...ian.org>, 
	Netdev <netdev@...r.kernel.org>
Subject: Re: Bug#1103242: /bin/ip: "ip mon" does not exit when output is gone

On Wed, 16 Apr 2025 at 00:06, Simon Richter <sjr@...ian.org> wrote:
>
> Hi,
>
> On 15.04.25 23:35, Luca Boccassi wrote:
>
> >> I started "ip mon" in the background, and closed the shell and the terminal.
>
> >> The "ip" command is still running, receiving netlink messages and writing to
stdout, receiving EIO for this attempt.
>
> >> Monitor mode should probably exit when it cannot write output.
>
> > Isn't this normal behaviour? IE, if I do 'sleep infinity &' and close
> > the terminal, it will likewise hang around
>
> Yes, but "sleep" will eventually exit, and doesn't produce output, so it
> doesn't have an opportunity to notice that stdout has been revoked.
>
> And since the only function in monitor mode is to produce this output,
> it can just exit here.

I see - then this is more like a feature request than a
packaging/downstream regression/issue.

Stephen, David, what do you think about the above request?