From: Steve Grubb <sgrubb@redhat.com>
To: Paul Moore <paul@paul-moore.com>, linux-audit@redhat.com
Subject: Re: New bug in Audit
Date: Mon, 09 Jan 2023 10:08:04 -0500 [thread overview]
Message-ID: <8169595.T7Z3S40VBb@x2> (raw)
In-Reply-To: <CAHC9VhQH28r_fOCaW+=_65M2SBNpVnQqcvxKt28Zc1+YEqwjBQ@mail.gmail.com>
On Friday, January 6, 2023 3:33:18 PM EST Paul Moore wrote:
> > This mailing list is *focused* on upstream work and support, and while
> > it does not preclude talking about distro specific bugs, I believe
> > there are better avenues for those discussions (e.g. see the RHBZ link
> > I provided in my response) as upstream isn't really going to be able
> > to provide adequate help for someone experiencing problems with a
> > distro kernel which has a number of patches and backports.
> >
> > If you have a problem with this approach, perhaps we should move
> > upstream development to an audit mailing list on vger.kernel.org and
> > leave this list for RH specific issues?
>
> Steve, I realize it's only been ~24hrs, but should I assume you are
> okay with that (the upstream focused approach)?
For the 18 years I've spent on this mail list, it has alway been open to any
topic audit related. I've answered questions for many distributions. If I can
reproduce the issue, then it's a bug worth looking at. If I can't reproduce
it, I let them know. I've even answered questions for people writing their
own audit implementation.
A lot of the email is upstream kernel work - no doubt. But Many times, we
miss upstream kernel bugs because no one is running upstream code. We usually
hear about it when a distribution which stays close to upstream releases a
new update.
The text where you sign up for this mail list does not limit the topc to
upstream work, it allows for any discussion as long as it's audit related. I
do not think making a new mail list is in anyone's interest. Bugs will always
get misreported if there are 2 lists.
-Steve
--
Linux-audit mailing list
Linux-audit@redhat.com
https://listman.redhat.com/mailman/listinfo/linux-audit
next prev parent reply other threads:[~2023-01-09 15:59 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-05 9:46 New bug in Audit Ariel Silver
2023-01-05 15:41 ` Paul Moore
2023-01-05 16:31 ` Steve Grubb
2023-01-05 19:32 ` Paul Moore
2023-01-06 20:33 ` Paul Moore
2023-01-09 8:30 ` Ariel Silver
2023-01-09 15:02 ` Paul Moore
2023-01-09 15:08 ` Steve Grubb [this message]
2023-01-10 4:38 ` Paul Moore
2023-01-06 0:35 ` Richard Guy Briggs
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=8169595.T7Z3S40VBb@x2 \
--to=sgrubb@redhat.com \
--cc=linux-audit@redhat.com \
--cc=paul@paul-moore.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.