Re: [patch] fix data corruption bug in __block_write_full_page()

On Tue, Jan 02, 2007 at 01:06:34PM +0100, Ingo Molnar wrote:
> Find it below - it's ontop of the tracer included in 2.6.20-rc2-rt3. 
> it's very ad-hoc, based on Linus' test utility. I can write such a 
> tracer in 30 minutes so i usually throw them away. I literally wrote 
> dozens of tracer variants for specific bugs in the past few years.

Ah, I though this was a general purpose tracer.  Question solved, thanks :)

I was just tired of writing my own special purpose tracers all the time
aswell.

-
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] fix data corruption bug in __block_write_full_page()
    • From: Christoph Hellwig <[email protected]>
  • Re: [patch] fix data corruption bug in __block_write_full_page()
    • From: Ingo Molnar <[email protected]>

• Prev by Date: [PATCH] isdn: capi kfree_skb cleanup
• Next by Date: Re: [PATCH] Open Firmware device tree virtual filesystem
• Previous by thread: Re: [patch] fix data corruption bug in __block_write_full_page()
• Next by thread: [PATCH] ppc: prom of_node_(get|put) cleanup
• 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]