From: viro@parcelfarce.linux.theplanet.co.uk
To: Oleg Drokin <green@linuxhacker.ru>
Cc: trond.myklebust@fys.uio.no, linux-kernel@vger.kernel.org
Subject: Re: NFS & long symlinks = stack overflow
Date: Sat, 15 May 2004 14:53:18 +0100 [thread overview]
Message-ID: <20040515135318.GP17014@parcelfarce.linux.theplanet.co.uk> (raw)
In-Reply-To: <20040515132149.GA14880@linuxhacker.ru>
On Sat, May 15, 2004 at 04:21:49PM +0300, Oleg Drokin wrote:
> Hello!
>
> For some time already I am investigating problems where fsstress run on
> NFS where NFSD is run on ext3 crashes in something like a hour.
> (but does not crash on reiserfs). On x86 crash looks like stack overflow
> (deref of pointer with last 3 digits being zero in kmap directly after
> get_current() call on 2.4.2x).
>
> Finally I was able to reduce a test case to two simple operations
> that reproduce the problem 100% reliably:
>
> [root@ranma root]# mount ranma:/testing /mnt -t nfs
> [root@ranma root]# cd /mnt
> [root@ranma mnt]# perl -e 'symlink("a"x4095, "f")'; ls -la f
> Segmentation fault
>
> (btw if you try to pass in something like 4090 worth of symbols, then
> subsequent ls won't crash, but last few symbols of link content will be
> corrupted)
Lovely. The real limit imposed by client (apparently not enforced, though)
is PAGE_CACHE_SIZE - 4 - 1. What are the protocol limits? I've been looking
into the same area for other reasons just now and all I could find was NFS v2
"no more than 1024 bytes", no information on v3 or v4.
Trond?
next prev parent reply other threads:[~2004-05-15 13:53 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-15 13:21 NFS & long symlinks = stack overflow Oleg Drokin
2004-05-15 13:53 ` viro [this message]
2004-05-15 17:26 ` Trond Myklebust
[not found] <1W7yE-3lZ-13@gated-at.bofh.it>
[not found] ` <1W7S5-3Am-13@gated-at.bofh.it>
2004-05-15 14:30 ` Pascal Schmidt
2004-05-15 14:53 ` viro
2004-05-15 17:37 ` Trond Myklebust
2004-05-15 20:19 ` Oleg Drokin
2004-05-16 4:41 ` Linus Torvalds
2004-05-16 4:55 ` viro
2004-05-16 22:20 ` Trond Myklebust
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=20040515135318.GP17014@parcelfarce.linux.theplanet.co.uk \
--to=viro@parcelfarce.linux.theplanet.co.uk \
--cc=green@linuxhacker.ru \
--cc=linux-kernel@vger.kernel.org \
--cc=trond.myklebust@fys.uio.no \
/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.