From: Willem de Bruijn <willemdebruijn.kernel@gmail.com>
To: Paul Moore <paul@paul-moore.com>, Ondrej Mosnacek <omosnace@redhat.com>
Cc: Willem de Bruijn <willemdebruijn.kernel@gmail.com>,
stsp <stsp2@yandex.ru>, Willem de Bruijn <willemb@google.com>,
Jason Wang <jasowang@redhat.com>,
Jakub Kicinski <kuba@kernel.org>,
network dev <netdev@vger.kernel.org>,
Linux Security Module list
<linux-security-module@vger.kernel.org>,
SElinux list <selinux@vger.kernel.org>
Subject: Re: Possible mistake in commit 3ca459eaba1b ("tun: fix group permission check")
Date: Wed, 05 Feb 2025 22:04:45 -0500 [thread overview]
Message-ID: <67a426cdb29f1_199430294e5@willemb.c.googlers.com.notmuch> (raw)
In-Reply-To: <CAHC9VhRF0bka4zY5y1uNYUGXNSSwz6cdta+c0NH_YDO0MxauRg@mail.gmail.com>
Paul Moore wrote:
> On Tue, Feb 4, 2025 at 11:19 AM Ondrej Mosnacek <omosnace@redhat.com> wrote:
> > On Tue, Feb 4, 2025 at 1:30 AM Paul Moore <paul@paul-moore.com> wrote:
> > >
> > > If a revert is the best path forward for v6.14, do you think it would
> > > be possible to get this fixed this week, or do you expect it to take
> > > longer?
> >
> > Willem has already posted patches on netdev [1][2] (thanks!), so I
> > expect it will be fixed soon.
You just beated me as I wrote a response :)
> Great, thanks everyone!
The revert has now just been merged to net.
next prev parent reply other threads:[~2025-02-06 3:04 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-27 9:10 Possible mistake in commit 3ca459eaba1b ("tun: fix group permission check") Ondrej Mosnacek
2025-01-27 10:00 ` stsp
2025-01-27 14:50 ` Willem de Bruijn
2025-01-27 14:58 ` stsp
2025-01-28 14:20 ` Ondrej Mosnacek
2025-01-28 14:45 ` stsp
2025-01-28 14:58 ` stsp
2025-01-28 15:04 ` Willem de Bruijn
2025-01-28 17:49 ` stsp
2025-01-28 22:59 ` Willem de Bruijn
2025-01-29 6:59 ` stsp
2025-01-29 14:12 ` Willem de Bruijn
2025-01-29 14:27 ` stsp
2025-01-30 16:46 ` Willem de Bruijn
2025-02-04 0:29 ` Paul Moore
2025-02-04 16:18 ` Ondrej Mosnacek
2025-02-04 19:40 ` Paul Moore
2025-02-06 3:04 ` Willem de Bruijn [this message]
2025-01-29 14:19 ` Willem de Bruijn
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=67a426cdb29f1_199430294e5@willemb.c.googlers.com.notmuch \
--to=willemdebruijn.kernel@gmail.com \
--cc=jasowang@redhat.com \
--cc=kuba@kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=omosnace@redhat.com \
--cc=paul@paul-moore.com \
--cc=selinux@vger.kernel.org \
--cc=stsp2@yandex.ru \
--cc=willemb@google.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 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).