Re: Bad ext3/nfs DoS bug

> so I used your exploit and I could reproduce it on every 2.6 kernel, I
> tried so far. 

That must have been a lot of fscks.

> However with a 2.4 kernel I see the error messages, but it
> doesn't get remounted read-only. Did you run tests with 2.4 kernels?

no, I don't have any to hand, but someone is preparing one
now. Is NFS subtree checking on by default in 2.4?

James.
-
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: Bad ext3/nfs DoS bug
    • From: Marcel Holtmann <[email protected]>

• References:
  • Bad ext3/nfs DoS bug
    • From: James <[email protected]>
  • Re: Bad ext3/nfs DoS bug
    • From: Marcel Holtmann <[email protected]>

• Prev by Date: Re: kernel/timer.c: next_timer_interrupt() strange/buggy(?) code (2.6.18-rc1-mm2)
• Next by Date: RE: Generic B-tree implementation
• Previous by thread: Re: Bad ext3/nfs DoS bug
• Next by thread: Re: Bad ext3/nfs DoS bug
• 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]