netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Raju Rangoju <rajur@chelsio.com>
To: netdev@vger.kernel.org
Cc: hch@lst.de, rahul.lakkireddy@chelsio.com, rajur@chelsio.com
Subject: how to determine if buffers are in user-space/kernel-space
Date: Mon, 18 Jan 2021 23:56:37 +0530	[thread overview]
Message-ID: <20210118182636.GB15369@chelsio.com> (raw)

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?


Thanks in Advance,
Raju

[1]
https://patchwork.kernel.org/project/linux-fsdevel/patch/20200817073212.830069-10-hch@lst.de/

             reply	other threads:[~2021-01-18 18:42 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-18 18:26 Raju Rangoju [this message]
2021-01-19  2:20 ` how to determine if buffers are in user-space/kernel-space Stephen Hemminger

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=20210118182636.GB15369@chelsio.com \
    --to=rajur@chelsio.com \
    --cc=hch@lst.de \
    --cc=netdev@vger.kernel.org \
    --cc=rahul.lakkireddy@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).