All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tim Cooijmans <tim@aapopfiets.nl>
To: kernel-janitors@vger.kernel.org
Subject: Re: [KJ] [PATCH] check request_region return value
Date: Sat, 25 Feb 2006 20:42:01 +0000	[thread overview]
Message-ID: <200602252142.02236.tim@aapopfiets.nl> (raw)
In-Reply-To: <200602242249.22568.tim@aapopfiets.nl>

On Saturday 25 February 2006 18:34, Jesper Juhl wrote:
> Ahh yes, looking a bit more closely at the code I see that's true.
> Hmm, there's got to be a cleaner way, the result of your patch is a
> pretty ugly error path...
Pretty much the only alternative I can think of is something like this: 

if (condition && request_region(x)) {
        if (condition && request_region(y)) {
                /* ... */
        } else {
                release_region(x);
        }
}

In this case, it will become a nine-level deep nest, and it's not much 
different from my original version.

Having done some research, I don't think the checks are necessary.  
request_region() (actually __request_resource()) does some checks which I'm 
pretty sure will catch any 0 passed to it.  The GPE odd/even checks will 
still have to be done, though.

I'll make a patch without most of the checks, unless anyone objects to 
removing them.

Tim
_______________________________________________
Kernel-janitors mailing list
Kernel-janitors@lists.osdl.org
https://lists.osdl.org/mailman/listinfo/kernel-janitors

  parent reply	other threads:[~2006-02-25 20:42 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-02-24 21:49 [KJ] [PATCH] check request_region return value Tim Cooijmans
2006-02-24 21:58 ` Jesper Juhl
2006-02-24 23:07 ` Tim Cooijmans
2006-02-24 23:11 ` Jesper Juhl
2006-02-25 13:58 ` Tim Cooijmans
2006-02-25 14:13 ` Jesper Juhl
2006-02-25 17:26 ` Tim Cooijmans
2006-02-25 17:34 ` Jesper Juhl
2006-02-25 20:42 ` Tim Cooijmans [this message]
2006-02-25 21:03 ` Jesper Juhl
2006-02-26  4:50 ` Darren Jenkins\
2006-02-26 19:52 ` Tim Cooijmans

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=200602252142.02236.tim@aapopfiets.nl \
    --to=tim@aapopfiets.nl \
    --cc=kernel-janitors@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 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.