Re: [2.6 patch] OCFS2: __init / __exit problem

> 
> This is the common problem that such error paths are only used once 
> every dozen years and therefore get no real testing coverage...


Rusty presented some brilliant tool for this at OLS this year... I bet
that could be used for filesystems as well (Rusty uses it for netfilter
testing)

-
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: [2.6 patch] OCFS2: __init / __exit problem
    • From: "Randy.Dunlap" <[email protected]>

• References:
  • OCFS2: __init / __exit problem
    • From: Jan-Benedict Glaw <[email protected]>
  • [2.6 patch] OCFS2: __init / __exit problem
    • From: Adrian Bunk <[email protected]>
  • Re: [2.6 patch] OCFS2: __init / __exit problem
    • From: Mark Fasheh <[email protected]>
  • Re: [2.6 patch] OCFS2: __init / __exit problem
    • From: Adrian Bunk <[email protected]>

• Prev by Date: Re: 2.6.15-mm2
• Next by Date: [2.6 patch] fs/libfs.c: unexport simple_rename
• Previous by thread: Re: [2.6 patch] OCFS2: __init / __exit problem
• Next by thread: Re: [2.6 patch] OCFS2: __init / __exit problem
• 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]