From: Eric Dumazet <edumazet@google.com>
To: "zhangpeng (AS)" <zhangpeng362@huawei.com>
Cc: Matthew Wilcox <willy@infradead.org>,
linux-mm@kvack.org, linux-fsdevel@vger.kernel.org,
netdev@vger.kernel.org, akpm@linux-foundation.org,
davem@davemloft.net, dsahern@kernel.org, kuba@kernel.org,
pabeni@redhat.com, arjunroy@google.com,
wangkefeng.wang@huawei.com
Subject: Re: SECURITY PROBLEM: Any user can crash the kernel with TCP ZEROCOPY
Date: Thu, 25 Jan 2024 11:31:42 +0100 [thread overview]
Message-ID: <CANn89iLThLScqJh0YSC0W3d2M6DrPzYeX3ViL7UM2BDiNbiWTA@mail.gmail.com> (raw)
In-Reply-To: <531c536d-a7d1-2be5-10aa-8d6eb4dcb5c9@huawei.com>
On Thu, Jan 25, 2024 at 10:22 AM zhangpeng (AS) <zhangpeng362@huawei.com> wrote:
>
>
> This patch can fix this issue.
>
>
Great, I will submit this patch for review then, thanks a lot !
>
> If all the pages that need to be inserted by TCP zerocopy are
> page->mapping == NULL, this solution could be used.
At least the patch looks sane for stable submission.
If we need to extend functionality, it can be done in future kernels.
prev parent reply other threads:[~2024-01-25 10:31 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-19 9:20 [RFC PATCH] filemap: add mapping_mapped check in filemap_unaccount_folio() Peng Zhang
2024-01-19 13:40 ` Matthew Wilcox
2024-01-20 6:46 ` zhangpeng (AS)
2024-01-22 16:04 ` SECURITY PROBLEM: Any user can crash the kernel with TCP ZEROCOPY Matthew Wilcox
2024-01-22 16:30 ` Eric Dumazet
2024-01-22 17:12 ` Matthew Wilcox
2024-01-22 17:39 ` Eric Dumazet
2024-01-24 9:30 ` zhangpeng (AS)
2024-01-24 10:11 ` Eric Dumazet
2024-01-25 2:18 ` zhangpeng (AS)
2024-01-25 8:57 ` Eric Dumazet
2024-01-25 9:22 ` zhangpeng (AS)
2024-01-25 10:31 ` Eric Dumazet [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=CANn89iLThLScqJh0YSC0W3d2M6DrPzYeX3ViL7UM2BDiNbiWTA@mail.gmail.com \
--to=edumazet@google.com \
--cc=akpm@linux-foundation.org \
--cc=arjunroy@google.com \
--cc=davem@davemloft.net \
--cc=dsahern@kernel.org \
--cc=kuba@kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=wangkefeng.wang@huawei.com \
--cc=willy@infradead.org \
--cc=zhangpeng362@huawei.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