From: David Gibson <david@gibson.dropbear.id.au>
To: Paul Holzinger <pholzing@redhat.com>
Cc: passt-dev@passt.top
Subject: Re: [PATCH] tap: include errno in error when tap_ns_tun() fails
Date: Thu, 3 Aug 2023 12:28:39 +1000 [thread overview]
Message-ID: <ZMsQ12GbQBk6o2Zd@zatzit> (raw)
In-Reply-To: <7ddb3b35-58fe-a376-f839-d9fc6de9ffc5@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 2329 bytes --]
On Wed, Aug 02, 2023 at 11:51:02AM +0200, Paul Holzinger wrote:
>
> On 02/08/2023 03:39, David Gibson wrote:
> > On Tue, Aug 01, 2023 at 01:50:17PM +0200, Paul Holzinger wrote:
> > > It is important to know why a syscall failed so pasta should include the
> > > errno in the error message. This is still not perfect as we do not know
> > > which of functions (open, ioctl, if_nametoindex) failed but it should at
> > > least include more important context.
> > Uh.. we certainly want this, but I don't think this implementation
> > will quite do it.
> >
> > > This change was inspiered by a podman issue[1].
> > >
> > > [1] https://github.com/containers/podman/issues/19428
> > >
> > > Signed-off-by: Paul Holzinger <pholzing@redhat.com>
> > > ---
> > > tap.c | 3 ++-
> > > 1 file changed, 2 insertions(+), 1 deletion(-)
> > >
> > > diff --git a/tap.c b/tap.c
> > > index a6a73d3..c212616 100644
> > > --- a/tap.c
> > > +++ b/tap.c
> > > @@ -1205,7 +1205,8 @@ static void tap_sock_tun_init(struct ctx *c)
> > > NS_CALL(tap_ns_tun, c);
> > NS_CALL means we're running the function in an ephemeral
> > thread/process/thingy..
> >
> > > if (tun_ns_fd == -1)
> > > - die("Failed to open tun socket in namespace");
> > > + die("Failed to open tun socket in namespace: %s",
> > > + strerror(errno));
> > ..which means we can't rely on it actually setting errno in the
> > original process. The ephemeral thread does share memory, but modern
> > errno is a weird per-thread thingy, so I'm not entirely sure what will
> > happen here, but I'm certainly not confident about it working as we'd
> > like.
> >
> > I'll have a crack at a more robust approach today.
>
> Thanks, I only did a quick test with chmod 600 /dev/net/tun and got the
> expected EACCES so I assumed it worked fine
Huh, interesting, maybe it does work. Unless some earlier syscall
happened to set errno to EACCES.
> but anyway your series looks
> much better.
Yeah, I realized as I was working on it that that approach has the
additional advantage of clearly showing which operation failed.
--
David Gibson | I'll have my music baroque, and my code
david AT gibson.dropbear.id.au | minimalist, thank you. NOT _the_ _other_
| _way_ _around_!
http://www.ozlabs.org/~dgibson
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
prev parent reply other threads:[~2023-08-03 2:33 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-01 11:50 [PATCH] tap: include errno in error when tap_ns_tun() fails Paul Holzinger
2023-08-02 1:39 ` David Gibson
2023-08-02 9:51 ` Paul Holzinger
2023-08-03 2:28 ` David Gibson [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=ZMsQ12GbQBk6o2Zd@zatzit \
--to=david@gibson.dropbear.id.au \
--cc=passt-dev@passt.top \
--cc=pholzing@redhat.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.
Code repositories for project(s) associated with this public inbox
https://passt.top/passt
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 IMAP folder(s).