From: Sergey Shtylyov <s.shtylyov@omp.ru>
To: Zheng Hacker <hackerzheng666@gmail.com>, Lee Jones <lee@kernel.org>
Cc: Jakub Kicinski <kuba@kernel.org>, Zheng Wang <zyytlz.wz@163.com>,
<davem@davemloft.net>, <linyunsheng@huawei.com>,
<edumazet@google.com>, <pabeni@redhat.com>,
<netdev@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<1395428693sheep@gmail.com>, <alex000young@gmail.com>
Subject: Re: [PATCH net v3] net: ravb: Fix possible UAF bug in ravb_remove
Date: Sat, 15 Jul 2023 23:48:25 +0300 [thread overview]
Message-ID: <a116e972-dfcf-6923-1ad3-a40870e02f6a@omp.ru> (raw)
In-Reply-To: <CAJedcCzRVSW7_R5WN0v3KdUQGdLEA88T3V2YUKmQO+A+uCQU8Q@mail.gmail.com>
On 7/15/23 7:07 PM, Zheng Hacker wrote:
> Sorry for my late reply. I'll see what I can do later.
That's good to hear!
Because I'm now only able to look at it during weekends...
> Lee Jones <lee@kernel.org> 于2023年7月12日周三 19:56写道：
>>
>> On Mon, 10 Jul 2023, Jakub Kicinski wrote:
>>
>>> On Mon, 10 Jul 2023 12:42:53 +0100 Lee Jones wrote:
>>>> For better or worse, it looks like this issue was assigned a CVE.
>>>
>>> Ugh, what a joke.
>>
>> I think that's putting it politely. :)
>>
>> --
>> Lee Jones [李琼斯]
MBR, Sergey
next prev parent reply other threads:[~2023-07-15 20:48 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-11 18:06 Zheng Wang
2023-03-12 20:26 ` Sergey Shtylyov
2023-03-13 3:00 ` Zheng Hacker
2023-03-13 1:15 ` Yunsheng Lin
2023-03-13 3:02 ` Zheng Hacker
2023-03-13 3:32 ` Yunsheng Lin
2023-03-13 9:34 ` Zheng Hacker
2023-07-19 21:04 ` Sergey Shtylyov
2023-03-13 22:39 ` Jakub Kicinski
2023-03-14 1:24 ` Zheng Hacker
2023-07-05 8:05 ` Lee Jones
2023-07-10 11:42 ` Lee Jones
2023-07-10 16:15 ` Jakub Kicinski
2023-07-11 21:20 ` Sergey Shtylyov
2023-07-12 11:56 ` Lee Jones
2023-07-15 16:07 ` Zheng Hacker
2023-07-15 20:48 ` Sergey Shtylyov [this message]
2023-07-16 2:11 ` Zheng Hacker
2023-07-16 3:14 ` Zheng Hacker
2023-07-17 13:04 ` Lee Jones
2023-07-17 13:21 ` Zheng Hacker
2023-07-24 9:20 ` Lee Jones
2023-07-25 2:26 ` Zheng Hacker
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=a116e972-dfcf-6923-1ad3-a40870e02f6a@omp.ru \
--to=s.shtylyov@omp.ru \
--cc=1395428693sheep@gmail.com \
--cc=alex000young@gmail.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=hackerzheng666@gmail.com \
--cc=kuba@kernel.org \
--cc=lee@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linyunsheng@huawei.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=zyytlz.wz@163.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
all inboxes | Powered by JetHome®