All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kuniyuki Iwashima <kuniyu@amazon.com>
To: <willemdebruijn.kernel@gmail.com>
Cc: <brauner@kernel.org>, <davem@davemloft.net>,
	<edumazet@google.com>, <horms@kernel.org>, <kuba@kernel.org>,
	<kuni1840@gmail.com>, <kuniyu@amazon.com>,
	<netdev@vger.kernel.org>, <pabeni@redhat.com>,
	<willemb@google.com>
Subject: Re: [PATCH v3 net-next 9/9] selftest: af_unix: Test SO_PASSRIGHTS.
Date: Thu, 15 May 2025 13:50:08 -0700	[thread overview]
Message-ID: <20250515205016.90052-1-kuniyu@amazon.com> (raw)
In-Reply-To: <6826401ac346c_25ebe5294c3@willemb.c.googlers.com.notmuch>

From: Willem de Bruijn <willemdebruijn.kernel@gmail.com>
Date: Thu, 15 May 2025 15:27:22 -0400
> > @@ -227,10 +297,18 @@ void __send_fd(struct __test_metadata *_metadata,
> >  		.msg_control = &cmsg,
> >  		.msg_controllen = CMSG_SPACE(sizeof(cmsg.fd)),
> >  	};
> > -	int ret;
> > +	int ret, saved_errno;
> >  
> > +	errno = 0;
> >  	ret = sendmsg(self->fd[receiver * 2 + 1], &msg, variant->flags);
> > -	ASSERT_EQ(MSGLEN, ret);
> > +	saved_errno = errno;
> > +
> > +	if (variant->disabled) {
> > +		ASSERT_EQ(-1, ret);
> > +		ASSERT_EQ(-EPERM, -saved_errno);
> > +	} else {
> > +		ASSERT_EQ(MSGLEN, ret);
> > +	}
> 
> Why is this errno complexity needed?
> 
> It should never be needed to manually reset errno.
> 
> Is the saved_errno there because ASSERT_EQ on ret could call a libc
> function that resets errno?

I guess it's paranoid here.

When ASSERT_EQ() calls TH_LOG(), it always fails and does
not reach the 2nd ASSERT_EQ().

Will remove them.

Thanks!

      reply	other threads:[~2025-05-15 20:50 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-05-14 16:51 [PATCH v3 net-next 0/9] af_unix: Introduce SO_PASSRIGHTS Kuniyuki Iwashima
2025-05-14 16:51 ` [PATCH v3 net-next 1/9] af_unix: Factorise test_bit() for SOCK_PASSCRED and SOCK_PASSPIDFD Kuniyuki Iwashima
2025-05-15 18:07   ` Willem de Bruijn
2025-05-15 20:23     ` Kuniyuki Iwashima
2025-05-15 21:48       ` Willem de Bruijn
2025-05-14 16:51 ` [PATCH v3 net-next 2/9] af_unix: Don't pass struct socket to maybe_add_creds() Kuniyuki Iwashima
2025-05-15 18:07   ` Willem de Bruijn
2025-05-14 16:51 ` [PATCH v3 net-next 3/9] scm: Move scm_recv() from scm.h to scm.c Kuniyuki Iwashima
2025-05-15 18:08   ` Willem de Bruijn
2025-05-14 16:51 ` [PATCH v3 net-next 4/9] tcp: Restrict SO_TXREHASH to TCP socket Kuniyuki Iwashima
2025-05-15 18:36   ` Willem de Bruijn
2025-05-14 16:51 ` [PATCH v3 net-next 5/9] net: Restrict SO_PASS{CRED,PIDFD,SEC} to AF_{UNIX,NETLINK,BLUETOOTH} Kuniyuki Iwashima
2025-05-15 18:36   ` Willem de Bruijn
2025-05-14 16:51 ` [PATCH v3 net-next 6/9] af_unix: Move SOCK_PASS{CRED,PIDFD,SEC} to struct sock Kuniyuki Iwashima
2025-05-15  3:18   ` Kuniyuki Iwashima
2025-05-15 18:44   ` Willem de Bruijn
2025-05-15 20:35     ` Kuniyuki Iwashima
2025-05-15 22:07       ` Willem de Bruijn
2025-05-15 22:15         ` Kuniyuki Iwashima
2025-05-14 16:51 ` [PATCH v3 net-next 7/9] af_unix: Inherit sk_flags at connect() Kuniyuki Iwashima
2025-05-15 19:06   ` Willem de Bruijn
2025-05-14 16:51 ` [PATCH v3 net-next 8/9] af_unix: Introduce SO_PASSRIGHTS Kuniyuki Iwashima
2025-05-15 19:25   ` Willem de Bruijn
2025-05-15 20:38     ` Kuniyuki Iwashima
2025-05-14 16:51 ` [PATCH v3 net-next 9/9] selftest: af_unix: Test SO_PASSRIGHTS Kuniyuki Iwashima
2025-05-15 19:27   ` Willem de Bruijn
2025-05-15 20:50     ` Kuniyuki Iwashima [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=20250515205016.90052-1-kuniyu@amazon.com \
    --to=kuniyu@amazon.com \
    --cc=brauner@kernel.org \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=horms@kernel.org \
    --cc=kuba@kernel.org \
    --cc=kuni1840@gmail.com \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=willemb@google.com \
    --cc=willemdebruijn.kernel@gmail.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.