Re: [PATCH] - catch blocks beyond pagecache limit in __getblk_slow

Eric Sandeen wrote:
> https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=206328
> 
> has a nice analysis of what can go wrong when we try to read blocks which
> are at extremely high offsets, when our sector_t is 64 bits but our pgoff_t
> is only 32.  The cases in question that I've seen are the result of filesystem
> corruption.

Urk, scratch that I see a fix is already in.

http://git.kernel.org/git/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commitdiff;h=e5657933863f43cc6bb76a54d659303dafaa9e58

-Eric
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

---

• References:
  • [PATCH] - catch blocks beyond pagecache limit in __getblk_slow
    • From: Eric Sandeen <[email protected]>

• Prev by Date: [PATCH] - catch blocks beyond pagecache limit in __getblk_slow
• Next by Date: Re: [PATCH 1/1] Net: kconfig, correct traffic shaper
• Previous by thread: [PATCH] - catch blocks beyond pagecache limit in __getblk_slow
• Next by thread: Re: + net-uninline-xfrm_selector_match.patch added to -mm tree
• Index(es):
  • Date
  • Thread

[Index of Archives]     [Kernel Newbies]     [Netfilter]     [Bugtraq]     [Photo]     [Stuff]     [Gimp]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Video 4 Linux]     [Linux for the blind]     [Linux Resources]