From: Christoph Hellwig <hch@infradead.org>
To: "D. Wythe" <alibuda@linux.alibaba.com>
Cc: "David S. Miller" <davem@davemloft.net>,
Andrew Morton <akpm@linux-foundation.org>,
Dust Li <dust.li@linux.alibaba.com>,
Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
Sidraya Jayagond <sidraya@linux.ibm.com>,
Uladzislau Rezki <urezki@gmail.com>,
Wenjia Zhang <wenjia@linux.ibm.com>,
Mahanta Jambigi <mjambigi@linux.ibm.com>,
Simon Horman <horms@kernel.org>,
Tony Lu <tonylu@linux.alibaba.com>,
Wen Gu <guwen@linux.alibaba.com>,
linux-kernel@vger.kernel.org, linux-mm@kvack.org,
linux-rdma@vger.kernel.org, linux-s390@vger.kernel.org,
netdev@vger.kernel.org, oliver.yang@linux.alibaba.com
Subject: Re: [PATCH net-next 2/3] mm: vmalloc: export find_vm_area()
Date: Fri, 23 Jan 2026 06:44:52 -0800 [thread overview]
Message-ID: <aXOJZBZCjjsbv7-e@infradead.org> (raw)
In-Reply-To: <20260123082349.42663-3-alibuda@linux.alibaba.com>
On Fri, Jan 23, 2026 at 04:23:48PM +0800, D. Wythe wrote:
> find_vm_area() provides a way to find the vm_struct associated with a
> virtual address. Export this symbol to modules so that modularized
> subsystems can perform lookups on vmalloc addresses.
No, they have absolutely no business doing that. This functionality
is very intentionally kept private.
next prev parent reply other threads:[~2026-01-23 14:45 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-23 8:23 [PATCH net-next 0/3] net/smc: buffer allocation and registration improvements D. Wythe
2026-01-23 8:23 ` [PATCH net-next 1/3] net/smc: cap allocation order for SMC-R physically contiguous buffers D. Wythe
2026-01-23 10:54 ` Alexandra Winter
2026-01-24 9:22 ` D. Wythe
2026-01-23 8:23 ` [PATCH net-next 2/3] mm: vmalloc: export find_vm_area() D. Wythe
2026-01-23 14:44 ` Christoph Hellwig [this message]
2026-01-23 18:55 ` Uladzislau Rezki
2026-01-24 9:35 ` D. Wythe
2026-01-24 10:48 ` Uladzislau Rezki
2026-01-24 14:57 ` D. Wythe
2026-01-26 10:28 ` Uladzislau Rezki
2026-01-26 12:02 ` D. Wythe
2026-01-26 16:45 ` Uladzislau Rezki
2026-01-27 13:34 ` Leon Romanovsky
2026-01-28 3:45 ` D. Wythe
2026-01-28 11:13 ` Leon Romanovsky
2026-01-28 12:44 ` D. Wythe
2026-01-28 13:49 ` Leon Romanovsky
2026-01-29 11:03 ` D. Wythe
2026-01-29 12:22 ` Leon Romanovsky
2026-01-29 14:04 ` D. Wythe
2026-01-28 18:06 ` Jason Gunthorpe
2026-01-29 11:36 ` D. Wythe
2026-01-29 13:20 ` Jason Gunthorpe
2026-01-30 8:51 ` D. Wythe
2026-01-30 15:16 ` Jason Gunthorpe
2026-02-03 9:14 ` D. Wythe
2026-01-23 8:23 ` [PATCH net-next 3/3] net/smc: optimize MTTE consumption for SMC-R buffers D. Wythe
2026-01-23 14:52 ` Christoph Hellwig
2026-01-24 9:25 ` D. Wythe
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=aXOJZBZCjjsbv7-e@infradead.org \
--to=hch@infradead.org \
--cc=akpm@linux-foundation.org \
--cc=alibuda@linux.alibaba.com \
--cc=davem@davemloft.net \
--cc=dust.li@linux.alibaba.com \
--cc=edumazet@google.com \
--cc=guwen@linux.alibaba.com \
--cc=horms@kernel.org \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-rdma@vger.kernel.org \
--cc=linux-s390@vger.kernel.org \
--cc=mjambigi@linux.ibm.com \
--cc=netdev@vger.kernel.org \
--cc=oliver.yang@linux.alibaba.com \
--cc=pabeni@redhat.com \
--cc=sidraya@linux.ibm.com \
--cc=tonylu@linux.alibaba.com \
--cc=urezki@gmail.com \
--cc=wenjia@linux.ibm.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