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 17:26:42 +0000 [thread overview]
Message-ID: <200602251826.43230.tim@aapopfiets.nl> (raw)
In-Reply-To: <200602242249.22568.tim@aapopfiets.nl>
On Saturday 25 February 2006 15:13, Jesper Juhl wrote:
> > +out_gpe1_blk:
> > + if (acpi_gbl_FADT->xgpe0_blk.address &&
> > acpi_gbl_FADT->gpe0_blk_len && + !(acpi_gbl_FADT->gpe0_blk_len
> > & 0x1))
> > + release_region(acpi_gbl_FADT->xgpe0_blk.address,
> > + acpi_gbl_FADT->gpe0_blk_len);
> > +out_gpe0_blk:
> > + if (acpi_gbl_FADT->xpm2_cnt_blk.address &&
> > acpi_gbl_FADT->pm2_cnt_len) +
> > release_region(acpi_gbl_FADT->xpm2_cnt_blk.address, +
> > acpi_gbl_FADT->pm2_cnt_len);
> > +out_pm2_cnt_blk:
> > + if (acpi_gbl_FADT->xpm_tmr_blk.address &&
> > acpi_gbl_FADT->pm_tm_len = 4) +
> > release_region(acpi_gbl_FADT->xpm_tmr_blk.address, 4); +out_pm_tmr:
> > + if (acpi_gbl_FADT->xpm1b_cnt_blk.address &&
> > acpi_gbl_FADT->pm1_cnt_len) +
> > release_region(acpi_gbl_FADT->xpm1b_cnt_blk.address, +
> > acpi_gbl_FADT->pm1_cnt_len);
> > +out_pm1b_cnt_blk:
> > + if (acpi_gbl_FADT->xpm1a_cnt_blk.address &&
> > acpi_gbl_FADT->pm1_cnt_len) +
> > release_region(acpi_gbl_FADT->xpm1a_cnt_blk.address, +
> > acpi_gbl_FADT->pm1_cnt_len);
> > +out_pm1a_cnt_blk:
> > + if (acpi_gbl_FADT->xpm1b_evt_blk.address &&
> > acpi_gbl_FADT->pm1_evt_len) +
> > release_region(acpi_gbl_FADT->xpm1b_evt_blk.address, +
> > acpi_gbl_FADT->pm1_evt_len);
> > +out_pm1b_evt_blk:
> > + if (acpi_gbl_FADT->xpm1a_evt_blk.address &&
> > acpi_gbl_FADT->pm1_evt_len) +
> > release_region(acpi_gbl_FADT->xpm1a_evt_blk.address, +
> > acpi_gbl_FADT->pm1_evt_len);
> > +out_pm1a_evt_blk:
> > + return -EBUSY;
> > }
>
> Why all these if's in the error path? Since you get to any of these
> labels in the first place you already know what request_region()s
> succeeded, so what's the point of checking all these variables before
> calling release_region()?
Not all request_region()s are tried. These checks are done before requesting
them as well, to determine which ones should be requested. If I don't do
these checks here, some release_region() calls will try to release regions
that were never requested.
I'll look into your other comments.
Thanks,
Tim
_______________________________________________
Kernel-janitors mailing list
Kernel-janitors@lists.osdl.org
https://lists.osdl.org/mailman/listinfo/kernel-janitors
next prev parent reply other threads:[~2006-02-25 17:26 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 [this message]
2006-02-25 17:34 ` Jesper Juhl
2006-02-25 20:42 ` Tim Cooijmans
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=200602251826.43230.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.