From: Hans Reiser <reiser@namesys.com>
To: Oleg Drokin <green@linuxhacker.ru>
Cc: akpm@osdl.org, aia21@cantab.net, blaisorblade@yahoo.it,
dhowells@redhat.com, dwmw2@infradead.org, hch@lst.de,
jdike@addtoit.com, linux-fsdevel@vger.kernel.org,
miklos@szeredi.hu, neilb@cse.unsw.edu.au,
reiserfs-dev@namesys.com, rmk@arm.linux.org.uk,
trond.myklebust@fys.uio.no, zippel@linux-m68k.org,
mm-commits@vger.kernel.org
Subject: Re: + fix-possible-page_cache_shift-overflows.patch added to -mm tree
Date: Fri, 25 Nov 2005 16:54:18 -0800 [thread overview]
Message-ID: <4387B23A.6000309@namesys.com> (raw)
In-Reply-To: <20051124112430.GM5297@linuxhacker.ru>
Oleg Drokin wrote:
>
>
>Please consider patch below:
>
>--- linux-2.6.14/fs/reiserfs/inode.c.orig 2005-11-24 13:26:26.000000000 +0200
>+++ linux-2.6.14/fs/reiserfs/inode.c 2005-11-24 13:28:35.000000000 +0200
>@@ -2194,7 +2194,7 @@ static int map_block_for_writepage(struc
> INITIALIZE_PATH(path);
> int pos_in_item;
> int jbegin_count = JOURNAL_PER_BALANCE_CNT;
>- loff_t byte_offset = (block << inode->i_sb->s_blocksize_bits) + 1;
>+ loff_t byte_offset = ((loff_t)block << inode->i_sb->s_blocksize_bits)+1;
> int retval;
> int use_get_block = 0;
> int bytes_copied = 0;
>
>
>Bye,
> Oleg
>
>
>
>
Thanks Oleg.
next prev parent reply other threads:[~2005-11-26 0:54 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-23 21:22 + fix-possible-page_cache_shift-overflows.patch added to -mm tree akpm
2005-11-23 22:01 ` ntfs - was: " Anton Altaparmakov
2005-11-24 1:00 ` Blaisorblade
2005-11-24 1:09 ` Andrew Morton
2005-11-24 1:37 ` Blaisorblade
2005-11-24 10:02 ` Christoph Hellwig
2005-11-24 7:05 ` Miklos Szeredi
2005-11-24 7:46 ` David Woodhouse
2005-11-24 11:24 ` Oleg Drokin
2005-11-26 0:54 ` Hans Reiser [this message]
2005-11-24 21:08 ` Roman Zippel
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=4387B23A.6000309@namesys.com \
--to=reiser@namesys.com \
--cc=aia21@cantab.net \
--cc=akpm@osdl.org \
--cc=blaisorblade@yahoo.it \
--cc=dhowells@redhat.com \
--cc=dwmw2@infradead.org \
--cc=green@linuxhacker.ru \
--cc=hch@lst.de \
--cc=jdike@addtoit.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=miklos@szeredi.hu \
--cc=mm-commits@vger.kernel.org \
--cc=neilb@cse.unsw.edu.au \
--cc=reiserfs-dev@namesys.com \
--cc=rmk@arm.linux.org.uk \
--cc=trond.myklebust@fys.uio.no \
--cc=zippel@linux-m68k.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).