From: Andrew Kanner <andrew.kanner@gmail.com>
To: Paul Moore <paul@paul-moore.com>
Cc: stephen.smalley.work@gmail.com, eparis@parisplace.org,
selinux@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-kernel-mentees@lists.linuxfoundation.org
Subject: Re: [PATCH 0/1] netlabel: KMSAN warning
Date: Wed, 16 Aug 2023 10:05:33 +0300 [thread overview]
Message-ID: <64dc7544.170a0220.90098.7253@mx.google.com> (raw)
In-Reply-To: <CAHC9VhRRcMQhbobpGZy0ha3saOJ4Ke1CCnExKSJq1E2jXCU3NQ@mail.gmail.com>
On Tue, Aug 15, 2023 at 06:27:43PM -0400, Paul Moore wrote:
>
> I think the answer is going to depend on the particular "bug" and the
> patch required to resolve it. In this particular case I think the
> patch is okay so I went ahead and merged it, although I did remove the
> "Fixes" tag as the current code isn't broken.
>
> In general, if a test tool dumps an error or warning for something
> under security/ and you aren't sure if it's valid or if we need to
> resolve it upstream, you can always send us an email and ask what to
> do :)
>
> --
> paul-moore.com
Thanks, Paul.
I got the idea.
--
Andrew Kanner
prev parent reply other threads:[~2023-08-16 7:06 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-15 20:59 [PATCH 0/1] netlabel: KMSAN warning Andrew Kanner
2023-08-15 20:59 ` [PATCH 1/1] selinux: netlabel: Prevent KMSAN warning in selinux_inet_conn_request() Andrew Kanner
2023-08-15 21:11 ` Greg KH
2023-08-15 21:53 ` Andrew Kanner
2023-08-15 22:23 ` Paul Moore
2023-08-15 22:27 ` [PATCH 0/1] netlabel: KMSAN warning Paul Moore
2023-08-16 7:05 ` Andrew Kanner [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=64dc7544.170a0220.90098.7253@mx.google.com \
--to=andrew.kanner@gmail.com \
--cc=eparis@parisplace.org \
--cc=linux-kernel-mentees@lists.linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=paul@paul-moore.com \
--cc=selinux@vger.kernel.org \
--cc=stephen.smalley.work@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox