From: Dan Clash <[email protected]>
To: Jens Axboe <[email protected]>, Paul Moore <[email protected]>
Cc: "[email protected]" <[email protected]>,
"[email protected]" <[email protected]>,
"[email protected]" <[email protected]>,
"[email protected]" <[email protected]>,
Dan Clash <[email protected]>
Subject: Re: [EXTERNAL] Re: audit: io_uring openat triggers audit reference count underflow in worker thread
Date: Thu, 12 Oct 2023 21:12:17 +0000 [thread overview]
Message-ID: <MW2PR2101MB103342BED5785C37F5F078B3F1D3A@MW2PR2101MB1033.namprd21.prod.outlook.com> (raw)
In-Reply-To: <[email protected]>
The patch will be sent from my alternate email address [email protected].
Paul and Jens, thank you for your guidance so far.
Dan
prev parent reply other threads:[~2023-10-12 21:12 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-06 20:09 audit: io_uring openat triggers audit reference count underflow in worker thread Dan Clash
2023-10-07 2:32 ` Jens Axboe
2023-10-07 13:11 ` Jens Axboe
2023-10-07 15:13 ` Paul Moore
2023-10-09 2:38 ` [EXTERNAL] " Dan Clash
2023-10-09 13:40 ` Jens Axboe
2023-10-12 21:12 ` Dan Clash [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=MW2PR2101MB103342BED5785C37F5F078B3F1D3A@MW2PR2101MB1033.namprd21.prod.outlook.com \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
/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