From: Gabriel Ryan <gabe@cs.columbia.edu>
To: Paul Moore <paul@paul-moore.com>
Cc: abhishek.shah@columbia.edu, linux-audit@redhat.com,
linux-kernel@vger.kernel.org, eparis@redhat.com
Subject: Re: data-race in audit_log_start / audit_receive
Date: Tue, 23 Aug 2022 09:09:54 -0400 [thread overview]
Message-ID: <CALbthtfc+j5PeV=oT+inpxxFehNS2c66UaQbQKtg1pA-+AFopg@mail.gmail.com> (raw)
In-Reply-To: <CAHC9VhQzb6Dtmmfw4kdiG9BCFzT9fkt=ms3us2p-eAsQv8gMiw@mail.gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 783 bytes --]
Hi Paul,
Will do. For this race we don’t have any indication it’s a serious problem
beyond the race itself and manual inspection of the relevant code locations.
Best,
Gabe
On Mon, Aug 22, 2022 at 7:42 PM Paul Moore <paul@paul-moore.com> wrote:
> On Mon, Aug 22, 2022 at 4:09 PM Gabriel Ryan <gabe@cs.columbia.edu> wrote:
> >
> > Hi Paul,
> >
> > Thanks for taking the time to review our report! It sounds like there
> > aren't severe negative impacts and patching to eliminate the race
> > would impose unnecessary performance penalties so we'll mark this as
> > benign for future reference.
>
> I just want to reiterate that if you are seeing a serious problem
> please let us know and we'll work with you to find a fix.
>
> --
> paul-moore.com
>
[-- Attachment #1.2: Type: text/html, Size: 1441 bytes --]
[-- Attachment #2: Type: text/plain, Size: 107 bytes --]
--
Linux-audit mailing list
Linux-audit@redhat.com
https://listman.redhat.com/mailman/listinfo/linux-audit
prev parent reply other threads:[~2022-08-24 13:05 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-18 22:23 data-race in audit_log_start / audit_receive Abhishek Shah
2022-08-19 1:59 ` Paul Moore
2022-08-19 12:06 ` Paul Moore
2022-08-22 20:09 ` Gabriel Ryan
2022-08-22 23:42 ` Paul Moore
2022-08-23 13:09 ` Gabriel Ryan [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='CALbthtfc+j5PeV=oT+inpxxFehNS2c66UaQbQKtg1pA-+AFopg@mail.gmail.com' \
--to=gabe@cs.columbia.edu \
--cc=abhishek.shah@columbia.edu \
--cc=eparis@redhat.com \
--cc=linux-audit@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--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 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 read-only IMAP folder(s) and NNTP newsgroup(s).