From: Jens Axboe <jens.axboe@oracle.com>
To: Tejun Heo <htejun@gmail.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] block: use jiffies conversion functions in scsi_ioctl.c
Date: Wed, 12 Dec 2007 08:27:39 +0100 [thread overview]
Message-ID: <20071212072738.GB4975@kernel.dk> (raw)
In-Reply-To: <475F5432.6020405@gmail.com>
On Wed, Dec 12 2007, Tejun Heo wrote:
> Jens Axboe wrote:
> > On Wed, Dec 05 2007, Tejun Heo wrote:
> >> Use msecs_to_jiffies() and jiffies_to_msecs() in scsi_ioctl().
> >> Sometimes callers use very large values for e.g. vendor specific media
> >> clear command and calculation can overflow.
> >
> > Thanks Tejun, applied.
>
> Jens, it seems premature timeout on bug 9346 could be caused by the same
> problem. Can you push this so that it can go into 2.6.24?
Certainly, it'll go in for 2.6.24. I'll push it out today.
--
Jens Axboe
prev parent reply other threads:[~2007-12-12 7:31 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-05 3:29 [PATCH] block: use jiffies conversion functions in scsi_ioctl.c Tejun Heo
2007-12-05 20:21 ` Jens Axboe
2007-12-12 3:23 ` Tejun Heo
2007-12-12 7:27 ` Jens Axboe [this message]
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=20071212072738.GB4975@kernel.dk \
--to=jens.axboe@oracle.com \
--cc=htejun@gmail.com \
--cc=linux-kernel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).