From: Ingo Molnar <mingo@elte.hu>
To: Cliff Wickman <cpw@sgi.com>
Cc: linux-kernel@vger.kernel.org, the arch/x86 maintainers <x86@kernel.org>
Subject: Re: [PATCHv6] SGI UV: TLB shootdown using broadcast assist unit - v6 delta
Date: Fri, 20 Jun 2008 13:34:57 +0200 [thread overview]
Message-ID: <20080620113457.GF7439@elte.hu> (raw)
In-Reply-To: <E1K9MoC-00049Z-KE@eag09.americas.sgi.com>
* Cliff Wickman <cpw@sgi.com> wrote:
> > Found a potential security hole while doing that:
> > static ssize_t uv_ptc_proc_write(struct file *file, const char __user *user,
> > size_t count, loff_t *data)
> > if (copy_from_user(optstr, user, count))
> > return -EFAULT;
> >
> > is count guaranteed to never be larger than 64?
> is fixed below.
applied to tip/x86/uv, thanks Cliff.
> It adds tlb_uv.o to the Makefile.
hm, it was already there in tip/master, so i left this bit out.
> char optstr[64];
>
> + if (count > 64)
> + return -EINVAL;
also, this should not be in /proc, but be moved to debugfs. See
arch/x86/mm/dump_pagetables.c about how to interface to debugfs.
And the "64" value should become something like:
static const int max_option_len = 64;
or so.
Ingo
prev parent reply other threads:[~2008-06-20 11:35 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-19 16:16 Cliff Wickman
2008-06-20 11:34 ` Ingo Molnar [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=20080620113457.GF7439@elte.hu \
--to=mingo@elte.hu \
--cc=cpw@sgi.com \
--cc=linux-kernel@vger.kernel.org \
--cc=x86@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
Powered by JetHome