From: Greg KH <greg@kroah.com>
To: David Howells <dhowells@redhat.com>
Cc: geert@linux-m68k.org, linux-kernel@vger.kernel.org, stable@kernel.org
Subject: Re: [stable] [PATCH] FS-Cache: Fix bounds check
Date: Wed, 13 Jul 2011 22:41:43 +0200 [thread overview]
Message-ID: <20110713204143.GC23159@kroah.com> (raw)
In-Reply-To: <20110713115518.29995.29712.stgit@warthog.procyon.org.uk>
On Wed, Jul 13, 2011 at 12:55:18PM +0100, David Howells wrote:
> __fscache_uncache_all_inode_pages() has a loop that goes through page index
> numbers go up to (loff_t)-1. This is incorrect. The limit should be
> (pgoff_t)-1 as on a 32-bit machine the pgoff_t is smaller than loff_t.
>
> On m68k the following error is observed:
>
> fs/fscache/page.c: In function '__fscache_uncache_all_inode_pages':
> fs/fscache/page.c:979: warning: comparison is always false due to
> limited range of data type
>
> [Should there be a PGOFF_T_MAX constant defined?]
>
> Reported-by: Geert Uytterhoeven <geert@linux-m68k.org>
> Signed-off-by: David Howells <dhowells@redhat.com>
> ---
>
> fs/fscache/page.c | 2 +-
> 1 files changed, 1 insertions(+), 1 deletions(-)
<formletter>
This is not the correct way to submit patches for inclusion in the
stable kernel tree. Please read Documentation/stable_kernel_rules.txt
for how to do this properly.
</formletter>
prev parent reply other threads:[~2011-07-13 20:43 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <201107072059.p67KxQ0O021814@hera.kernel.org>
2011-07-12 19:26 ` FS-Cache: Add a helper to bulk uncache pages on an inode Geert Uytterhoeven
2011-07-13 11:55 ` [PATCH] FS-Cache: Fix bounds check David Howells
2011-07-13 20:41 ` Greg KH [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=20110713204143.GC23159@kroah.com \
--to=greg@kroah.com \
--cc=dhowells@redhat.com \
--cc=geert@linux-m68k.org \
--cc=linux-kernel@vger.kernel.org \
--cc=stable@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.