From: Gnea <gnea@rochester.rr.com>
To: linux-kernel@vger.kernel.org
Subject: Re: [reiserfs-list] major security bug in reiserfs (may affect SuSE Linux)
Date: Wed, 10 Jan 2001 08:08:44 -0500 [thread overview]
Message-ID: <20010110080844.C8077@rochester.rr.com> (raw)
In-Reply-To: <20010110004201.A308@cerebro.laendle> <3A5BB340.9EA8B5C3@namesys.botik.ru>
In-Reply-To: <3A5BB340.9EA8B5C3@namesys.botik.ru>; from vs@namesys.botik.ru on Wed, Jan 10, 2001 at 03:56:32AM +0300
On Wed, Jan 10, 2001 at 03:56:32AM +0300, Vladimir V. Saveliev wrote:
> Hi
>
> Marc Lehmann wrote:
>
> > We are still investigating, but there seems to be a major security problem
>
> Hmm,
> mkdir "$(perl -e 'print "x" x 768')"
> ls
> echo *
>
> works here as it should. (2.2.18 and reiserfs-3.5.29)
cat /proc/version
Linux version 2.4.0-test11 (root@celery) (gcc version 2.95.2 20000220
(Debian GNU/Linux)) #1 SMP Fri Dec 15 01:45:43 EST 2000
snipping from dmesg:
reiserfs: checking transaction log (device 21:08) ...
Using tea hash to sort names
ReiserFS version 3.6.22
while mkdir "$(perl -e 'print "x" x 768')" works just fine, doing a
mkdir "$(perl -e 'print "x" x 4000')" will create the dir, but will NOT
segfault any program, NOR cause a kernel oops.. howeever, it will NOT
show up with ls. rm -rf "$(perl -e 'print "x" x 4000')" _will_ work...
i have yet to experience any crashes, segfaults or oopses since.
--
.oO Gnea [gnea at rochester dot rr dot com] Oo.
.oO url: http://garson.org/~gnea Oo.
"You can tune a filesystem, but you can't tuna fish." -unknown
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2001-01-10 13:12 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-09 23:42 major security bug in reiserfs (may affect SuSE Linux) Marc Lehmann
2001-01-10 0:43 ` [reiserfs-list] " John Morrison
2001-01-10 0:51 ` Chris Mason
2001-01-10 0:56 ` Vladimir V. Saveliev
2001-01-10 13:08 ` Gnea [this message]
2001-01-10 6:02 ` [BUGTRAQ] " John H. Robinson, IV
2001-01-10 11:03 ` [reiserfs-list] " Dirk Mueller
[not found] <20010110023208.B296@cerebro.laendle>
2001-01-10 2:23 ` Chris Mason
2001-01-10 4:43 ` David Ford
2001-01-10 5:47 ` Alexander Viro
2001-01-10 15:48 ` Chris Mason
2001-01-10 17:38 ` Alexander Viro
2001-01-10 18:48 ` Chris Mason
2001-01-11 0:47 ` Alexander Viro
2001-01-10 16:41 ` Andrea Arcangeli
2001-01-10 16:02 ` Vladimir V. Saveliev
2001-01-10 16:09 ` Chris Mason
2001-01-10 17:03 ` Stefan Traby
2001-01-10 17:11 ` Stefan Traby
2001-01-10 2:40 ` Chris Mason
2001-01-11 11:05 ` Hans Reiser
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=20010110080844.C8077@rochester.rr.com \
--to=gnea@rochester.rr.com \
--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