mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Leonidas ." <leonidas137@gmail.com>
To: linux-kernel <linux-kernel@vger.kernel.org>
Subject: Using intptr_t and uintptr_t in Kernel
Date: Tue, 13 Oct 2009 13:07:00 +0530	[thread overview]
Message-ID: <f22d86810910130037x48cac5c1s8928a6ff49dda381@mail.gmail.com> (raw)

Hello List,

I know variants of this questions have been asked on this list before,
but I could not
find a thread where a conclusion was reached, most of the time
responses were { I don't care,
developer's choice, might be in future } and variations thereof. But
one thing was clear
that do not mix userspace and kernel space data types.

Currently, I am porting a user space application to kernel, this app
uses intptr_t data type.

A look at linux/types.h shows that,

typedef unsigned long           uintptr_t;

but intptr_t is not defined at all. Also, isn't above definition
incorrect? Since the whole idea
behind uintptr_t is to store pointer in a int sized variable, are we
not assuming here that

sizeof(int) = sizeof(unsigned long ) on all archs? I have not worked
on all archs on which Linux
runs, but if that is the case then above definition is correct.

After looking at stdint.h (which is not available for kernel),

typedef __s32 intptr_t;
typedef __u32 uintptr_t;

sounds more appropriate. Please CMIIW.

-Leo.

             reply	other threads:[~2009-10-13  7:37 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-10-13  7:37 Leonidas . [this message]
2009-10-13  8:49 ` Mikael Pettersson
2009-10-13  8:58   ` Leonidas .
2009-10-13 11:47     ` Mikael Pettersson

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=f22d86810910130037x48cac5c1s8928a6ff49dda381@mail.gmail.com \
    --to=leonidas137@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    /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

all inboxes | Powered by JetHome®