From: Jens Axboe <[email protected]>
To: Pavel Begunkov <[email protected]>, [email protected]
Cc: Petr Vorel <[email protected]>
Subject: Re: [PATCH liburing] a test for CVE-2020-29373 (AF_UNIX path resolution)
Date: Fri, 12 Feb 2021 14:13:57 -0700 [thread overview]
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>
On 2/12/21 2:03 PM, Pavel Begunkov wrote:
> On 12/02/2021 21:02, Pavel Begunkov wrote:
>> Add a regression test for CVE-2020-29373 where io-wq do path resolution
>> issuing sendmsg, but doesn't have proper fs set up.
>
> Jens, what about licenses? The original test is GPLv2
That's fine, that's compatible. I just left the license blurb in there.
--
Jens Axboe
prev parent reply other threads:[~2021-02-12 21:14 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-12 21:02 [PATCH liburing] a test for CVE-2020-29373 (AF_UNIX path resolution) Pavel Begunkov
2021-02-12 21:03 ` Pavel Begunkov
2021-02-12 21:13 ` Jens Axboe [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 \
[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