From: Eric Sandeen <sandeen@sandeen.net>
To: Neil Brown <neilb@suse.de>
Cc: Andrew Morton <akpm@osdl.org>, Theodore Tso <tytso@mit.edu>,
jack@suse.cz, 20@madingley.org, marcel@holtmann.org,
linux-kernel@vger.kernel.org, sct@redhat.com,
adilger@clusterfs.com
Subject: Re: Bad ext3/nfs DoS bug
Date: Wed, 26 Jul 2006 12:12:18 -0500 [thread overview]
Message-ID: <44C7A272.8030401@sandeen.net> (raw)
In-Reply-To: <17605.32781.909741.310735@cse.unsw.edu.au>
> +EXPORT_SYMBOL_GPL(export_iget);
...
> +static struct dentry *ext3_get_dentry(struct super_block *sb, void *vobjp)
> +{
> + __u32 *objp = vobjp;
> + unsigned long ino = objp[0];
> + __u32 generation = objp[1];
> +
> + if (ino != EXT3_ROOT_INO && ino < EXT3_FIRST_INO(sb))
> + return ERR_PTR(-ESTALE);
> +
> + return export_iget(sb, ino, generation);
> +}
Hm, with this, ext3.ko has a new dependency on exportfs.ko. Is that
desirable/acceptable?
-Eric
next prev parent reply other threads:[~2006-07-26 17:12 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
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 [this message]
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=44C7A272.8030401@sandeen.net \
--to=sandeen@sandeen.net \
--cc=20@madingley.org \
--cc=adilger@clusterfs.com \
--cc=akpm@osdl.org \
--cc=jack@suse.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=marcel@holtmann.org \
--cc=neilb@suse.de \
--cc=sct@redhat.com \
--cc=tytso@mit.edu \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.