From: Michael Veeck <michael.veeck@gmx.net>
To: "Randy.Dunlap" <rddunlap@osdl.org>
Cc: Bartlomiej Zolnierkiewicz <B.Zolnierkiewicz@elka.pw.edu.pl>,
linux-ide@vger.kernel.org, Kernel-janitors@lists.osdl.org
Subject: Re: [janitor] use kernel min/max (2/2)
Date: Thu, 22 Apr 2004 01:31:46 +0200 [thread overview]
Message-ID: <40870462.5070807@gmx.net> (raw)
In-Reply-To: <20040421144605.517d5834.rddunlap@osdl.org>
Randy.Dunlap wrote:
> On Thu, 18 Mar 2004 18:17:59 +0100 Bartlomiej Zolnierkiewicz wrote:
>
> |
> | > @@ -354,7 +354,7 @@ static int idescsi_end_request (ide_driv
> | > if (!test_bit(PC_WRITING, &pc->flags) && pc->actually_transferred &&
> | > pc->actually_transferred <= 1024 && pc->buffer) { printk(", rst = ");
> | > scsi_buf = pc->scsi_cmd->request_buffer;
> | > - hexdump(scsi_buf, IDE_MIN(16, pc->scsi_cmd->request_bufflen));
> | > + hexdump(scsi_buf, min_t(int, 16, pc->scsi_cmd->request_bufflen));
> | > } else printk("\n");
> | > }
> | > }
> |
> | 'unsigned' should be used instead of 'int'
> | (scsi_cmd->request_bufflen is 'unsigned')
> |
> | > @@ -371,7 +371,7 @@ static int idescsi_end_request (ide_driv
> | >
> | > static inline unsigned long get_timeout(idescsi_pc_t *pc)
> | > {
> | > - return IDE_MAX(WAIT_CMD, pc->timeout - jiffies);
> | > + return max_t(long, WAIT_CMD, pc->timeout - jiffies);
> | > }
> | >
> | > /*
> |
> | pc->timeout and jiffies are of 'unsigned long' type
> | so why 'long' is used here? Timer wrapping protection?
>
> Yes, I think so. (see below)
>
> | Otherwise patches look okay and I will push them to Linus
> | as soon as somebody explains this 'long' thing to me. :-)
>
> Michael hasn't replied on this AFAIK.
Sorry for being quiet, I'm busy right now looking for a new job.
Anyway, IIRC I choose 'long' because of the jiffies.h too, but I'm
willing to change that back to 'unsigned long'.
>
> 'long' looks correct to me, just based on include/linux/jiffies.h.
> In that case, someone has thought lots more about it than I have
> and concluded that while jiffies is stored as 'unsigned long',
> comparing times is correct when coerced (typecast) to long, as in:
>
> #define time_after(a,b) \
> (typecheck(unsigned long, a) && \
> typecheck(unsigned long, b) && \
> ((long)(b) - (long)(a) < 0))
>
> But if you think it's risky, let's just drop it.
>
> | If somebody is interested there are still related things to fix in IDE code:
> |
> | drivers/ide/ide-cd.c:
> | use 'unsigned' instead of 'int' for nskip, sectors_to_transfer, len variables
> |
> | ide-timing.h:
> | get rid of MIN()/MAX() macros, this should be done very carefully
> | as they are used for calculating timings
Where's the risk in that? An example would be very helpful.
Thanks for the help
Veeck
>
>
> --
> ~Randy
>
>
next prev parent reply other threads:[~2004-04-21 23:35 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-17 0:35 [janitor] use kernel min/max (2/2) Randy.Dunlap
2004-03-18 17:17 ` Bartlomiej Zolnierkiewicz
2004-04-21 21:46 ` Randy.Dunlap
2004-04-21 23:31 ` Michael Veeck [this message]
2004-04-22 0:36 ` Bartlomiej Zolnierkiewicz
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=40870462.5070807@gmx.net \
--to=michael.veeck@gmx.net \
--cc=B.Zolnierkiewicz@elka.pw.edu.pl \
--cc=Kernel-janitors@lists.osdl.org \
--cc=linux-ide@vger.kernel.org \
--cc=rddunlap@osdl.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