Re: [PATCH 1 of 2] block_page_mkwrite() Implementation V2

On Wed, 2007-05-16 at 11:19 +0100, David Howells wrote:
> The start and end points passed to block_prepare_write() delimit the region of
> the page that is going to be modified.  This means that prepare_write()
> doesn't need to fill it in if the page is not up to date. 

Really? Is it _really_ going to be modified? Even if the pointer
userspace gave to write() is bogus, and is going to fault half-way
through the copy_from_user()?

-- 
dwmw2

-
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/

---

• Follow-Ups:
  • Re: [PATCH 1 of 2] block_page_mkwrite() Implementation V2
    • From: Chris Mason <[email protected]>

• References:
  • Re: [PATCH 1 of 2] block_page_mkwrite() Implementation V2
    • From: David Howells <[email protected]>

• Prev by Date: Re: [PATCH] LogFS take three
• Next by Date: (NFS) BUG: at page-writeback.c:829 [Was: 2.6.22-rc1-mm1]
• Previous by thread: Re: [PATCH 1 of 2] block_page_mkwrite() Implementation V2
• Next by thread: Re: [PATCH 1 of 2] block_page_mkwrite() Implementation V2
• 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]