From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from us-smtp-delivery-124.mimecast.com (us-smtp-delivery-124.mimecast.com [170.10.133.124]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.lore.kernel.org (Postfix) with ESMTPS id 901D3C6379F for ; Mon, 9 Jan 2023 15:59:30 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1673279969; h=from:from:sender:sender:reply-to:subject:subject:date:date: message-id:message-id:to:to:cc:mime-version:mime-version: content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references:list-id:list-help: list-unsubscribe:list-subscribe:list-post; bh=1BHFPRO5kYNA6JWmeYhIQFEreTZGu+oqgzfqiCYam8A=; b=W1wk80BprvVPOgGDJAwvjmurj/F939hnDUPrW2HsQqLKLo9mKQFIhmD3Cz57zrYeQ8nqX0 LCy5ktkTxAtTjsVGyxsYN2/PrJ3Wh3mmAJsAzlnQXaXId+FTZE8K+7PjRjfjF/D6RxuwYU EbBvvOYIaBRGHzUyGW+fpvzYzEa45Qw= Received: from mimecast-mx02.redhat.com (mimecast-mx02.redhat.com [66.187.233.88]) by relay.mimecast.com with ESMTP with STARTTLS (version=TLSv1.2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id us-mta-498-tlbb9AiLMS2QZanFWYmArw-1; Mon, 09 Jan 2023 10:59:28 -0500 X-MC-Unique: tlbb9AiLMS2QZanFWYmArw-1 Received: from smtp.corp.redhat.com (int-mx07.intmail.prod.int.rdu2.redhat.com [10.11.54.7]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mimecast-mx02.redhat.com (Postfix) with ESMTPS id CCE018030CF; Mon, 9 Jan 2023 15:59:26 +0000 (UTC) Received: from mm-prod-listman-01.mail-001.prod.us-east-1.aws.redhat.com (unknown [10.30.29.100]) by smtp.corp.redhat.com (Postfix) with ESMTP id C4B1F140EBF5; Mon, 9 Jan 2023 15:59:25 +0000 (UTC) Received: from mm-prod-listman-01.mail-001.prod.us-east-1.aws.redhat.com (localhost [IPv6:::1]) by mm-prod-listman-01.mail-001.prod.us-east-1.aws.redhat.com (Postfix) with ESMTP id 8C7631947BBC; Mon, 9 Jan 2023 15:59:25 +0000 (UTC) Received: from smtp.corp.redhat.com (int-mx05.intmail.prod.int.rdu2.redhat.com [10.11.54.5]) by mm-prod-listman-01.mail-001.prod.us-east-1.aws.redhat.com (Postfix) with ESMTP id 7A19F1946587 for ; Mon, 9 Jan 2023 15:59:24 +0000 (UTC) Received: by smtp.corp.redhat.com (Postfix) id 6D52242220; Mon, 9 Jan 2023 15:59:24 +0000 (UTC) Received: from x2.localnet (unknown [10.22.32.173]) by smtp.corp.redhat.com (Postfix) with ESMTPS id 3B85253AA; Mon, 9 Jan 2023 15:59:24 +0000 (UTC) From: Steve Grubb To: Paul Moore , linux-audit@redhat.com Subject: Re: New bug in Audit Date: Mon, 09 Jan 2023 10:08:04 -0500 Message-ID: <8169595.T7Z3S40VBb@x2> Organization: Red Hat In-Reply-To: References: MIME-Version: 1.0 X-Scanned-By: MIMEDefang 3.1 on 10.11.54.5 X-BeenThere: linux-audit@redhat.com X-Mailman-Version: 2.1.29 Precedence: list List-Id: Linux Audit Discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: linux-audit-bounces@redhat.com Sender: "Linux-audit" X-Scanned-By: MIMEDefang 3.1 on 10.11.54.7 X-Mimecast-Spam-Score: 0 X-Mimecast-Originator: redhat.com Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit 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