From: Lachlan McIlroy <lachlan@sgi.com>
To: Eric Sandeen <sandeen@sandeen.net>
Cc: xfs-oss <xfs@oss.sgi.com>
Subject: Re: [PATCH] Fix off by one error in page_region_mask()
Date: Fri, 05 Dec 2008 11:59:10 +1100 [thread overview]
Message-ID: <49387CDE.2030904@sgi.com> (raw)
In-Reply-To: <4937FAED.7060503@sandeen.net>
Eric Sandeen wrote:
> Lachlan McIlroy wrote:
>> final is calculated to be the last bit to set (ie inclusive) but when we
>> do the mask shifting final really needs to be first bit not to set.
>>
>> For example if first and final are both bit 0 (ie only first bit to be set)
>> then mask is completely shifted and becomes all zeroes.
>>
>> Or if first is 0 and final is 63 then the mask is shifted one bit when it
>> shouldn't be shifted at all.
>
> Lachlan, what's the end result of this bug? What's the broken behavior?
There was no observed bug - well nothing I can tie directly to this code.
I found this by inspection while investigating the page bitmap stuff.
We have a problem with ia64 going to 64K page size with filesystems that
use a filesystem sector size of 512 bytes - we don't have the granularity
we need in the bitmap.
I suppose it is possible this bug could indicate a page region is not up
to date when it actually is and we might re-read something from disk and
overwrite the more up to date in-memory version.
>
> Thanks,
> -Eric
>
>> --- xfs-fix.orig/fs/xfs/linux-2.6/xfs_buf.c
>> +++ xfs-fix/fs/xfs/linux-2.6/xfs_buf.c
>> @@ -129,15 +129,17 @@ page_region_mask(
>> int first, final;
>>
>> first = BTOPR(offset);
>> - final = BTOPRT(offset + length - 1);
>> - first = min(first, final);
>> + final = BTOPRT(offset + length);
>> +
>> + if (first >= final)
>> + return 0UL;
>>
>> mask = ~0UL;
>> mask <<= BITS_PER_LONG - (final - first);
>> mask >>= BITS_PER_LONG - (final);
>>
>> ASSERT(offset + length <= PAGE_CACHE_SIZE);
>> - ASSERT((final - first) < BITS_PER_LONG && (final - first) >= 0);
>> + ASSERT((final - first) <= BITS_PER_LONG && (final - first) > 0);
>>
>> return mask;
>> }
>>
>> _______________________________________________
>> xfs mailing list
>> xfs@oss.sgi.com
>> http://oss.sgi.com/mailman/listinfo/xfs
>>
>
>
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2008-12-05 4:47 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-04 7:48 [PATCH] Fix off by one error in page_region_mask() Lachlan McIlroy
2008-12-04 15:44 ` Eric Sandeen
2008-12-05 0:59 ` Lachlan McIlroy [this message]
2008-12-05 4:53 ` Eric Sandeen
2008-12-05 5:06 ` Lachlan McIlroy
2008-12-08 4:42 ` Timothy Shimmin
2008-12-08 5:16 ` Lachlan McIlroy
2008-12-22 8:53 ` Christoph Hellwig
2008-12-23 0:23 ` Lachlan McIlroy
2009-01-19 6:53 ` Lachlan McIlroy
2009-01-22 22:25 ` Christoph Hellwig
2009-02-15 19:16 ` Christoph Hellwig
2009-02-16 17:14 ` Felix Blyakher
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=49387CDE.2030904@sgi.com \
--to=lachlan@sgi.com \
--cc=sandeen@sandeen.net \
--cc=xfs@oss.sgi.com \
/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.