From: Stephen Hemminger <stephen@networkplumber.org>
To: Raju Rangoju <rajur@chelsio.com>
Cc: netdev@vger.kernel.org, hch@lst.de, rahul.lakkireddy@chelsio.com
Subject: Re: how to determine if buffers are in user-space/kernel-space
Date: Mon, 18 Jan 2021 18:20:44 -0800 [thread overview]
Message-ID: <20210118182044.26d59491@hermes.local> (raw)
In-Reply-To: <20210118182636.GB15369@chelsio.com>
On Mon, 18 Jan 2021 23:56:37 +0530
Raju Rangoju <rajur@chelsio.com> wrote:
> Hi,
>
> We have an out-of-tree kernel module which was using
> segment_eq(get_fs(), KERNEL_DS) to determine whether buffers are in
> Kernel space vs User space. However, with the get_fs() and its friends
> removed[1], we are out of ideas on how to determine if buffers are in
> user space or kernel space. Can someone shed some light on how to
> accomplish it?
>
Sorry, you are asking in the wrong place. Supporting any out of
tree modules is completely your own problem to deal with.
prev parent reply other threads:[~2021-01-19 2:21 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-18 18:26 how to determine if buffers are in user-space/kernel-space Raju Rangoju
2021-01-19 2:20 ` Stephen Hemminger [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=20210118182044.26d59491@hermes.local \
--to=stephen@networkplumber.org \
--cc=hch@lst.de \
--cc=netdev@vger.kernel.org \
--cc=rahul.lakkireddy@chelsio.com \
--cc=rajur@chelsio.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.