Re: [PATCH 2/2] Fix i_state of inode is changed after the inode is freed [try #2]

>> Are the patches going to be merged?
>
>Yep, they're queued up for 2.6.19.  Since it was a race found
>only on testing with a ramdisk (iirc) it didn't really seem to
>me like they needed to be rushed through for a 2.6.18-rc.  The
>race has also been there for the entire lifetime of the Linux
>XFS port... so, not urgent (and not risk free either).

Thanks, I agree it.  I'm looking forward to receiving the TAKE.
So far thank you, Nathan.  I wish to be glorious in your future.

cheers.

--
Masayuki
-
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:
- Re: [PATCH 2/2] Fix i_state of inode is changed after the inode is freed [try #2]
  - From: Nathan Scott <[email protected]>

Prev by Date: AW: [PATCH] sun disk label: fix signed int usage for sector count
Next by Date: Re: Linux v2.6.18-rc5
Previous by thread: Re: [PATCH 2/2] Fix i_state of inode is changed after the inode is freed [try #2]
Next by thread: [patch 0/5] RFC: fault-injection capabilities
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]