From: Oleg Drokin <green@namesys.com>
To: Reiserfs mail-list <Reiserfs-List@Namesys.COM>
Subject: Re: Reserved Blocks
Date: Thu, 26 Sep 2002 10:19:42 +0400 [thread overview]
Message-ID: <20020926101942.A5436@namesys.com> (raw)
In-Reply-To: <m31y7ij62k.fsf@multivac.cwru.edu>
Hello!
On Wed, Sep 25, 2002 at 02:07:41PM -0400, Paul Jarc wrote:
> > Also consider there is set uid application that outputs data.
> > I just do setuid_app >>/fs_to_fill/somefile
> > and repeat it that much times to fill the fs.
> That won't work. The open() for the ">>" output redirection is done
It should.
> by the shell, not the setuid program. But if the setuid program lets
That's right. But the program that writes into that file is setuid program.
And blocks are allocated by that setuid program.
This is only works if you can create files of fs you want to fiil of course.
At least that's my current belief ;)
Bye,
Oleg
next prev parent reply other threads:[~2002-09-26 6:19 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-16 10:27 Reserved Blocks Sam Vilain
2002-09-16 10:32 ` Oleg Drokin
2002-09-16 10:48 ` Nikita Danilov
[not found] ` <20020916125116.B8E96297C@hofmann.snowcra.sh>
2002-09-16 13:15 ` Nikita Danilov
2002-09-16 13:41 ` Oleg Drokin
2002-09-25 18:07 ` Paul Jarc
2002-09-26 6:19 ` Oleg Drokin [this message]
2002-09-26 6:55 ` Matthias Urlichs
2002-09-26 7:02 ` Oleg Drokin
2002-09-26 7:59 ` Matthias Urlichs
2002-09-26 8:03 ` Oleg Drokin
2002-09-26 8:05 ` Matthias Urlichs
[not found] ` <15749.55656.692129.840162@laputa.namesys.com>
2002-09-16 14:00 ` Sam Vilain
2002-09-16 14:50 ` Valdis.Kletnieks
[not found] ` <200209161713.52352.russell@coker.com.au>
2002-09-16 15:35 ` Valdis.Kletnieks
2002-09-16 15:44 ` Russell Coker
2002-09-16 16:23 ` Sam Vilain
2002-09-16 16:43 ` Russell Coker
2002-09-16 16:14 ` Sam Vilain
2002-09-16 16:48 ` Russell Coker
[not found] ` <200209161651.g8GGpKM4005169@turing-police.cc.vt.edu>
2002-09-17 17:39 ` Sam Vilain
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=20020926101942.A5436@namesys.com \
--to=green@namesys.com \
--cc=Reiserfs-List@Namesys.COM \
/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.