From: Yunsheng Lin <linyunsheng@huawei.com>
To: "Toke Høiland-Jørgensen" <toke@redhat.com>,
"Yunsheng Lin" <yunshenglin0825@gmail.com>,
"David S. Miller" <davem@davemloft.net>,
"Jakub Kicinski" <kuba@kernel.org>,
"Jesper Dangaard Brouer" <hawk@kernel.org>,
"Saeed Mahameed" <saeedm@nvidia.com>,
"Leon Romanovsky" <leon@kernel.org>,
"Tariq Toukan" <tariqt@nvidia.com>,
"Andrew Lunn" <andrew+netdev@lunn.ch>,
"Eric Dumazet" <edumazet@google.com>,
"Paolo Abeni" <pabeni@redhat.com>,
"Ilias Apalodimas" <ilias.apalodimas@linaro.org>,
"Simon Horman" <horms@kernel.org>,
"Andrew Morton" <akpm@linux-foundation.org>,
"Mina Almasry" <almasrymina@google.com>,
"Yonglong Liu" <liuyonglong@huawei.com>,
"Pavel Begunkov" <asml.silence@gmail.com>,
"Matthew Wilcox" <willy@infradead.org>,
"Robin Murphy" <robin.murphy@arm.com>,
IOMMU <iommu@lists.linux.dev>,
segoon@openwall.com, solar@openwall.com,
oss-security@lists.openwall.com,
kernel-hardening@lists.openwall.com
Cc: <netdev@vger.kernel.org>, <bpf@vger.kernel.org>,
<linux-rdma@vger.kernel.org>, <linux-mm@kvack.org>,
Qiuling Ren <qren@redhat.com>, Yuying Ma <yuma@redhat.com>
Subject: Re: [PATCH net-next 3/3] page_pool: Track DMA-mapped pages and unmap them when destroying the pool
Date: Thu, 20 Mar 2025 19:17:47 +0800 [thread overview]
Message-ID: <7a604ae4-063f-48ff-a92f-014d1cf86adc@huawei.com> (raw)
In-Reply-To: <87r02ti57p.fsf@toke.dk>
On 2025/3/19 20:18, Toke Høiland-Jørgensen wrote:
>>
>> All I asked is about moving PP_MAGIC_MASK macro into poison.h if you
>> still want to proceed with reusing the page->pp_magic as the masking and
>> the signature to be masked seems reasonable to be in the same file.
>
> Hmm, my thinking was that this would be a lot of irrelevant stuff to put
> into poison.h, but I suppose we could do so if the mm folks don't object :)
The masking and the signature to be masked is correlated, I am not sure
what you meant by 'irrelevant stuff' here.
As you seemed to have understood most of my concern about reusing
page->pp_magic, I am not going to argue with you about the uncertainty
of security and complexity of different address layout for different
arches again.
But I am still think it is not the way forward with the reusing of
page->pp_magic through doing some homework about the 'POISON_POINTER'.
If you still think my idea is complex and still want to proceed with
reusing the space of page->pp_magic, go ahead and let the maintainers
decide if it is worth the security risk and performance degradation.
>
> -Toke
>
>
next prev parent reply other threads:[~2025-03-20 11:17 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-14 10:10 [PATCH net-next 0/3] Fix late DMA unmap crash for page pool Toke Høiland-Jørgensen
2025-03-14 10:10 ` [PATCH net-next 1/3] page_pool: Move pp_magic check into helper functions Toke Høiland-Jørgensen
2025-03-21 17:16 ` Mina Almasry
2025-03-14 10:10 ` [PATCH net-next 2/3] page_pool: Turn dma_sync and dma_sync_cpu fields into a bitmap Toke Høiland-Jørgensen
2025-03-15 9:31 ` Yunsheng Lin
2025-03-17 14:55 ` Toke Høiland-Jørgensen
2025-03-21 23:13 ` Mina Almasry
2025-03-14 10:10 ` [PATCH net-next 3/3] page_pool: Track DMA-mapped pages and unmap them when destroying the pool Toke Høiland-Jørgensen
2025-03-15 9:46 ` Yunsheng Lin
2025-03-17 15:16 ` Toke Høiland-Jørgensen
2025-03-18 12:39 ` Yunsheng Lin
2025-03-18 20:55 ` Toke Høiland-Jørgensen
2025-03-19 11:06 ` Yunsheng Lin
2025-03-19 12:18 ` Toke Høiland-Jørgensen
2025-03-20 11:17 ` Yunsheng Lin [this message]
2025-03-20 14:34 ` Toke Høiland-Jørgensen
2025-03-20 2:32 ` Solar Designer
2025-03-20 14:37 ` Toke Høiland-Jørgensen
2025-03-17 2:02 ` [PATCH net-next 0/3] Fix late DMA unmap crash for page pool Yonglong Liu
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=7a604ae4-063f-48ff-a92f-014d1cf86adc@huawei.com \
--to=linyunsheng@huawei.com \
--cc=akpm@linux-foundation.org \
--cc=almasrymina@google.com \
--cc=andrew+netdev@lunn.ch \
--cc=asml.silence@gmail.com \
--cc=bpf@vger.kernel.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=hawk@kernel.org \
--cc=horms@kernel.org \
--cc=ilias.apalodimas@linaro.org \
--cc=iommu@lists.linux.dev \
--cc=kernel-hardening@lists.openwall.com \
--cc=kuba@kernel.org \
--cc=leon@kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-rdma@vger.kernel.org \
--cc=liuyonglong@huawei.com \
--cc=netdev@vger.kernel.org \
--cc=oss-security@lists.openwall.com \
--cc=pabeni@redhat.com \
--cc=qren@redhat.com \
--cc=robin.murphy@arm.com \
--cc=saeedm@nvidia.com \
--cc=segoon@openwall.com \
--cc=solar@openwall.com \
--cc=tariqt@nvidia.com \
--cc=toke@redhat.com \
--cc=willy@infradead.org \
--cc=yuma@redhat.com \
--cc=yunshenglin0825@gmail.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