From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Jens Axboe <jens.axboe@oracle.com>
Cc: linuxppc-dev list <linuxppc-dev@ozlabs.org>
Subject: Warning in block code
Date: Wed, 17 Jun 2009 11:39:43 +1000 [thread overview]
Message-ID: <1245202783.21602.5.camel@pasglop> (raw)
Hoy !
I see that:
block/blk-settings.c: In function ‘blk_set_default_limits’:
block/blk-settings.c:115: warning: large integer implicitly truncated to unsigned type
Comes from
lim->bounce_pfn = BLK_BOUNCE_ANY;
With BLK_BOUNCE_ANY being a
include/linux/blkdev.h:#define BLK_BOUNCE_ANY (-1ULL)
And struct queue_limit.bounce_pfn is:
unsigned long bounce_pfn;
(The warning is fishy as both quantities are unsigned, but there -is- truncation
happening here).
Cheers,
Ben.
next reply other threads:[~2009-06-17 1:39 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-17 1:39 Benjamin Herrenschmidt [this message]
2009-06-17 4:36 ` Warning in block code Jens Axboe
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=1245202783.21602.5.camel@pasglop \
--to=benh@kernel.crashing.org \
--cc=jens.axboe@oracle.com \
--cc=linuxppc-dev@ozlabs.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).