Re: [PATCH 2/2] hugetlb: synchronize alloc with page cache insert

On Wed, Jan 11, 2006 at 04:24:23PM -0600, Adam Litke wrote:
> My only concern is if I am using the correct lock for the job here.

->i_lock looks rather fishy. It may have been necessary when ->i_blocks
was used for nefarious purposes, but without ->i_blocks fiddling, it's
not needed unless I somehow missed the addition of some custom fields
to hugetlbfs inodes and their modifications by any of these functions.


-- wli
-
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 2/2] hugetlb: synchronize alloc with page cache insert
  - From: Adam Litke <[email protected]>

References:
- Hugetlb: Shared memory race
  - From: Adam Litke <[email protected]>
- [PATCH 1/2] hugetlb: Delay page zeroing for faulted pages
  - From: Adam Litke <[email protected]>
- [PATCH 2/2] hugetlb: synchronize alloc with page cache insert
  - From: Adam Litke <[email protected]>

Prev by Date: Re: 2.6.15-mm3, current -git: drivers/media/video/ compile errors
Next by Date: Re: Kernel BUG at fs/sysfs/symlink.c:87 happens with 2.6.15 too
Previous by thread: [PATCH 2/2] hugetlb: synchronize alloc with page cache insert
Next by thread: Re: [PATCH 2/2] hugetlb: synchronize alloc with page cache insert
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]