From: viro@parcelfarce.linux.theplanet.co.uk
To: Keith Owens <kaos@ocs.com.au>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Local DoS on single_open?
Date: Thu, 11 Sep 2003 08:29:09 +0100 [thread overview]
Message-ID: <20030911072909.GT454@parcelfarce.linux.theplanet.co.uk> (raw)
In-Reply-To: <5196.1063263888@kao2.melbourne.sgi.com>
On Thu, Sep 11, 2003 at 05:04:48PM +1000, Keith Owens wrote:
> On Thu, 11 Sep 2003 14:51:09 +1000,
> Nick Piggin <piggin@cyberone.com.au> wrote:
> >Keith Owens wrote:
> >
> >>single_open() requires the kernel to kmalloc a buffer which lives until
> >>the userspace caller closes the file. What prevents a malicious user
> >>opening the same /proc entry multiple times, allocating lots of kmalloc
> >>space and causing a local DoS?
> >>
> >>
> >
> >ulimit?
>
> ulimit has no effect on kmalloc usage.
You do realize that struct file is also kmalloc'ed? So are dentries and
inodes, for that matter. It's the same situation as with pipes and sockets.
next prev parent reply other threads:[~2003-09-11 7:29 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-11 4:42 Local DoS on single_open? Keith Owens
2003-09-11 4:51 ` Nick Piggin
2003-09-11 7:04 ` Keith Owens
2003-09-11 7:29 ` viro [this message]
2003-09-11 4:55 ` viro
2003-09-11 7:26 ` Keith Owens
2003-09-11 7:32 ` viro
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=20030911072909.GT454@parcelfarce.linux.theplanet.co.uk \
--to=viro@parcelfarce.linux.theplanet.co.uk \
--cc=kaos@ocs.com.au \
--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