From: John Belmonte <john@neggie.net>
To: "Barry K. Nathan" <barryn@pobox.com>
Cc: linux-kernel@vger.kernel.org, arjanv@redhat.com
Subject: Re: [PATCH] (2.6.x) toshiba_acpi needs copy_from_user (fixes oops)
Date: Sun, 14 Mar 2004 00:52:04 -0500 [thread overview]
Message-ID: <4053F304.5040903@neggie.net> (raw)
In-Reply-To: <20040314052510.GA2587@ip68-4-255-84.oc.oc.cox.net>
Thank you for tracking this down.
Please don't apply this patch to the kernel tree. I will submit a
variation via Len Brown. In any case, it appears at least one other
ACPI driver has a similar bug, so best to go through Len.
-John
Barry K. Nathan wrote:
> On kernels with the 4G/4G patch (like some of the recent kernels in
> Fedora Core 2 development), writing stuff to the /proc/acpi/toshiba/*
> files causes an oops. As it turns out, this is because the driver is
> accessing userspace data without first doing copy_from_user(). IOW, this
> is a bug in toshiba_acpi, not a bug in the 4G/4G patch.
>
> Here's a patch to fix this bug. I've tested it on 2.6.4 + some patches
> from the FC kernels (including the 4G/4G patch) and it fixes my oopses.
> I have also tested it against vanilla 2.6.4 and I haven't encountered
> any regressions.
>
> If there are any problems with this patch, let me know.
>
> -Barry K. Nathan <barryn@pobox.com>
>
>
> diff -ruN linux-2.6.4/drivers/acpi/toshiba_acpi.c linux-2.6.4-bkn1/drivers/acpi/toshiba_acpi.c
> --- linux-2.6.4/drivers/acpi/toshiba_acpi.c 2004-03-12 21:31:59.000000000 -0800
> +++ linux-2.6.4-bkn1/drivers/acpi/toshiba_acpi.c 2004-03-12 22:27:07.000000000 -0800
> @@ -41,6 +41,7 @@
> #include <linux/init.h>
> #include <linux/types.h>
> #include <linux/proc_fs.h>
> +#include <asm/uaccess.h>
>
> #include <acpi/acpi_drivers.h>
>
> @@ -269,10 +270,18 @@
> }
>
> static int
> -dispatch_write(struct file* file, const char* buffer, unsigned long count,
> - ProcItem* item)
> +dispatch_write(struct file* file, const char __user *buffer,
> + unsigned long count, ProcItem* item)
> {
> - return item->write_func(buffer, count);
> + char str[48] = {'\0'};
> +
> + if (count > sizeof(str) - 1)
> + return count;
> +
> + if (copy_from_user(str, buffer, count))
> + return -EFAULT;
> +
> + return item->write_func(str, count);
> }
>
> static char*
>
>
--
http:// if ile.org/
next prev parent reply other threads:[~2004-03-14 5:52 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-14 5:25 [PATCH] (2.6.x) toshiba_acpi needs copy_from_user (fixes oops) Barry K. Nathan
2004-03-14 5:52 ` John Belmonte [this message]
2004-03-14 7:10 ` Barry K. Nathan
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=4053F304.5040903@neggie.net \
--to=john@neggie.net \
--cc=arjanv@redhat.com \
--cc=barryn@pobox.com \
--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