mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Randy Dunlap <rdunlap@xenotime.net>
To: Rofail Qu <rofail@gmail.com>
Cc: linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: A simple question of sys_
Date: Fri, 17 Sep 2010 11:55:23 -0700	[thread overview]
Message-ID: <20100917115523.3f583f8d.rdunlap@xenotime.net> (raw)
In-Reply-To: <AANLkTintKaxaAKarDPFgpDLQMVomhThYtZecp5R5Mi62@mail.gmail.com>

On Fri, 17 Sep 2010 14:58:30 +0800 Rofail Qu wrote:

> How to use macro IS_ERR() ?
> 
> It defines as,
> ...
> #define IS_ERR_VALUE(x) unlikely((x) >= (unsigned long)-MAX_ERRNO)
> static inline long __must_check IS_ERR(const void *ptr)
> {
> 	return IS_ERR_VALUE((unsigned long)ptr);
> }
> ...
> so when pass x as a pointer and x>=-MAX_ERRNO (including NULL or any
> valid address),
> IS_ERR() will return true!

Since your conclusion is false, some part of your premise must have a problem.
Can you find it?


> IS_ERR(x) seems to use on judge if "x" is a valid error number, right?

Yes, that's what it is for.

> So in sys_execve(),
> ...
>         long error;
> 	char* filename;
> 
> 	filename = getname(name);
> 	error = PTR_ERR(filename);
> 	if (IS_ERR(filename))     // <== should be IS_ERR((void *)error) or other?
> 		return error;
> 	error = do_execve(filename, argv, envp, regs);
> ...
> 
> Where i am wrong?


---
~Randy
*** Remember to use Documentation/SubmitChecklist when testing your code ***

  reply	other threads:[~2010-09-17 18:55 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-09-17  6:58 Rofail Qu
2010-09-17 18:55 ` Randy Dunlap [this message]
2010-09-20  8:34   ` Rofail Qu
2010-09-20 15:28     ` Randy Dunlap
2010-09-20  7:48 ` Américo Wang
2010-09-20  8:28   ` Rofail Qu
2010-09-21  7:53     ` Américo Wang

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=20100917115523.3f583f8d.rdunlap@xenotime.net \
    --to=rdunlap@xenotime.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rofail@gmail.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

all inboxes | Powered by JetHome®