All of lore.kernel.org
 help / color / mirror / Atom feed
From: Namhyung Kim <namhyung@gmail.com>
To: Arnd Bergmann <arnd@arndb.de>
Cc: Christoph Hellwig <hch@infradead.org>,
	Roland McGrath <roland@redhat.com>,
	Oleg Nesterov <oleg@redhat.com>,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/3 RESEND] ptrace: cleanup address space conversion on ptrace_request()
Date: Wed, 25 Aug 2010 16:48:40 +0900	[thread overview]
Message-ID: <87sk23w2sn.fsf@gmail.com> (raw)
In-Reply-To: <201008241345.06507.arnd@arndb.de> (Arnd Bergmann's message of "Tue, 24 Aug 2010 13:45:06 +0200")

Arnd Bergmann <arnd@arndb.de> writes:
> I don't think we ever rely on 'data' being signed, and user space
> sees it as 'void *' anyway, so it should be possible to just turn
> it into 'unsigned long'.
>

After I've checked all arch_ptrace() code, I can think there is no specific
reason @addr and @data to be signed long types. Most of archs use them
as if they were unsigned. So I'll prepare a patch series to change this
and some cleanups of ptrace_request() and all of arch_ptrace() if no
objection exists.

Thanks.

-- 
Regards,
Namhyung Kim

  reply	other threads:[~2010-08-25  7:48 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-08-22 10:22 [PATCH 2/3] ptrace: add __force markup Namhyung Kim
2010-08-22 20:06 ` Arnd Bergmann
2010-08-23 16:06   ` [PATCH 2/3 RESEND] ptrace: cleanup address space conversion on ptrace_request() Namhyung Kim
2010-08-23 16:21     ` Christoph Hellwig
2010-08-23 16:38       ` Namhyung Kim
2010-08-24 11:45         ` Arnd Bergmann
2010-08-25  7:48           ` Namhyung Kim [this message]
2010-08-25 11:42             ` Arnd Bergmann

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=87sk23w2sn.fsf@gmail.com \
    --to=namhyung@gmail.com \
    --cc=arnd@arndb.de \
    --cc=hch@infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=oleg@redhat.com \
    --cc=roland@redhat.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.