From: David Miller <davem@davemloft.net>
To: w@1wt.eu
Cc: DJurzitza@harmanbecker.com, linux-kernel@vger.kernel.org,
sparclinux@vger.kernel.org
Subject: Re: Patch 2.4 kernel / allow to read more than 2048 (1821) Symbols from /boot/System.map
Date: Thu, 21 Sep 2006 15:56:15 -0700 (PDT) [thread overview]
Message-ID: <20060921.155615.11378692.davem@davemloft.net> (raw)
In-Reply-To: <20060919182638.GD3467@1wt.eu>
From: Willy Tarreau <w@1wt.eu>
Date: Tue, 19 Sep 2006 20:26:38 +0200
> On Sun, Sep 17, 2006 at 10:35:12PM -0700, David Miller wrote:
> > From: "Jurzitza, Dieter" <DJurzitza@harmanbecker.com>
> > Date: Mon, 18 Sep 2006 07:23:58 +0200
> >
> > > The 2.4 kernel series uses sys32_get_kernel_syms(struct kernel_sym32
> > > *table) for reading the kernel symbols (on sparc64). The size of
> > > struct kernel_sym is 64 byte on "normal" arches, but 72 byte on
> > > sparc64.
> >
> > Jurzita, you do not need to post this patch multiple times.
> > I was simply on vacation for 2 weeks right after your first
> > posting so I had no chance to review the patch.
>
> BTW, did you finally review it (no emergency at all on my side) ?
There are two problems:
1) If this goes in, similar fixes for sys_ia32.c, mips64, et al.
should go in at the same time.
2) I dislike this fix because it means that users can lock down
a significant amount of non-swappable kernel memory. There are
no privilege checks in the get_kernel_syms() system call, so
anyone can invoke it. Imagine a fork bomb invoking this, and it
could also potentially eat up nearly all of the vmalloc() space.
It may be, in the end, simply better to have a
"compat_sys_get_kernel_syms" written that can be called
so a temporary kernel copy is not needed.
I'm not offering to implement this :-) But it does seem to be the
only reasonable solution.
prev parent reply other threads:[~2006-09-21 22:56 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-18 5:23 Jurzitza, Dieter
2006-09-18 5:35 ` David Miller
2006-09-19 18:26 ` Willy Tarreau
2006-09-21 22:56 ` David Miller [this message]
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=20060921.155615.11378692.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=DJurzitza@harmanbecker.com \
--cc=linux-kernel@vger.kernel.org \
--cc=sparclinux@vger.kernel.org \
--cc=w@1wt.eu \
/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
all inboxes | Powered by JetHome®