public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Marcel Holtmann <marcel@holtmann.org>
To: James <20@madingley.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Bad ext3/nfs DoS bug
Date: Tue, 18 Jul 2006 17:22:16 +0200	[thread overview]
Message-ID: <1153236136.10006.5.camel@localhost> (raw)
In-Reply-To: <20060718145614.GA27788@circe.esc.cam.ac.uk>

Hi James,

> > 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.

it wasn't that many. For some obvious reasons I only tested the RHEL and
Fedora kernels and vanilla plus stable series.

> > 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?

I haven't checked within the code, but the manual page exports(5) states
subtree checking as being on by default. And it doesn't mention any
difference to 2.4 kernels.

What is the reason behind your question? Does disabling subtree checking
changes something?

Regards

Marcel



  reply	other threads:[~2006-07-18 15:21 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-07-17 13:01 Bad ext3/nfs DoS bug James
2006-07-17 13:06 ` Marcel Holtmann
2006-07-17 18:43 ` Marcel Holtmann
2006-07-18  7:55 ` Marcel Holtmann
2006-07-18 14:56   ` James
2006-07-18 15:22     ` Marcel Holtmann [this message]
2006-07-18 15:23       ` James
2006-07-18 20:18         ` Marcel Holtmann
2006-07-19  9:28           ` James
2006-07-19 15:55             ` Jan Kara
2006-07-20  4:46               ` Neil Brown
2006-07-20 16:06                 ` Jan Kara
2006-07-20 20:11                   ` James
2006-07-21  6:44                     ` Neil Brown
2006-07-21  6:39                   ` Neil Brown
2006-07-21 14:24                     ` Jan Kara
2006-07-22  0:06                     ` Andrew Morton
2006-07-22 13:17                       ` Theodore Tso
2006-07-25  1:56                         ` Andrew Morton
2006-07-25  2:21                           ` Neil Brown
2006-07-26 17:12                             ` Eric Sandeen
2006-07-26 23:53                               ` Neil Brown
2006-07-27 18:32                                 ` Eric Sandeen
2006-07-27 19:12                                   ` Christoph Hellwig
2006-07-28  0:34                                     ` Neil Brown
2006-07-28 13:27                                     ` Peter Staubach
2006-07-28 13:30                                       ` Christoph Hellwig
2006-07-25  2:36                           ` Neil Brown
2006-07-25 18:27                             ` Eric Sandeen
2006-07-21  0:42                 ` Marcel Holtmann
2006-07-21 12:29                   ` Andrew Morton
  -- strict thread matches above, loose matches on Subject: below --
2006-07-22  3:38 linux

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1153236136.10006.5.camel@localhost \
    --to=marcel@holtmann.org \
    --cc=20@madingley.org \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox