From: Ralf Baechle DL5RB <ralf@linux-mips.org>
To: "Alejandro Colomar (man-pages)" <alx.manpages@gmail.com>
Cc: netdev@vger.kernel.org, linux-hams@vger.kernel.org,
Thomas Osterried <thomas@osterried.de>,
Michael Kerrisk <mtk.manpages@gmail.com>,
linux-man@vger.kernel.org
Subject: Re: [PATCH] packet.7: Describe SOCK_PACKET netif name length issues and workarounds.
Date: Thu, 29 Jul 2021 08:05:25 +0200 [thread overview]
Message-ID: <YQJFJWP5MnWrJr34@linux-mips.org> (raw)
In-Reply-To: <a050e248-af45-0678-b25c-27e249fb5565@gmail.com>
On Wed, Jul 28, 2021 at 10:52:15PM +0200, Alejandro Colomar (man-pages) wrote:
> Hello Ralf,
>
> On 7/27/21 10:53 AM, Ralf Baechle wrote:
> > Describe the issues with SOCK_PACKET possibly truncating network interface
> > names in results, solutions and possible workarounds.
> >
> > While the issue is know for a long time it appears to have never been
> > documented properly and is has started to bite software antiques badly since
> > the introduction of Predictable Network Interface Names. So let's document
> > it.
> >
> > Signed-off-by: Ralf Baechle <ralf@linux-mips.org>
>
> Thanks for the patch!
> Please see a few comments below.
I'll make an updated version in a week or so. Until then I'm goning to be
offline on civil defence duty in German's flood disaster region ...
Ralf
prev parent reply other threads:[~2021-07-29 6:05 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-27 8:53 [PATCH] packet.7: Describe SOCK_PACKET netif name length issues and workarounds Ralf Baechle
2021-07-28 20:52 ` Alejandro Colomar (man-pages)
2021-07-29 6:05 ` Ralf Baechle DL5RB [this message]
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=YQJFJWP5MnWrJr34@linux-mips.org \
--to=ralf@linux-mips.org \
--cc=alx.manpages@gmail.com \
--cc=linux-hams@vger.kernel.org \
--cc=linux-man@vger.kernel.org \
--cc=mtk.manpages@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=thomas@osterried.de \
/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).