From: akpm@linux-foundation.org
To: mm-commits@vger.kernel.org
Cc: dada1@cosmosbay.com
Subject: + parport-dev-timeslice-is-an-unsigned-long-not-an-int.patch added to -mm tree
Date: Tue, 11 Dec 2007 15:30:58 -0800 [thread overview]
Message-ID: <200712112331.lBBNV3SW014665@imap1.linux-foundation.org> (raw)
The patch titled
parport: "dev->timeslice" is an unsigned long, not an int
has been added to the -mm tree. Its filename is
parport-dev-timeslice-is-an-unsigned-long-not-an-int.patch
*** Remember to use Documentation/SubmitChecklist when testing your code ***
See http://www.zip.com.au/~akpm/linux/patches/stuff/added-to-mm.txt to find
out what to do about this
------------------------------------------------------
Subject: parport: "dev->timeslice" is an unsigned long, not an int
From: Eric Dumazet <dada1@cosmosbay.com>
While auditing proc_doulongvec_ms_jiffies_minmax() usage in kernel, I found
a bug in drivers/parport/procfs.c, incorrectly using sizeof(int) instead of
sizeof(unsigned long)
Only 64bit arches are affected by this old bug.
Signed-off-by: Eric Dumazet <dada1@cosmosbay.com>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
---
drivers/parport/procfs.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff -puN drivers/parport/procfs.c~parport-dev-timeslice-is-an-unsigned-long-not-an-int drivers/parport/procfs.c
--- a/drivers/parport/procfs.c~parport-dev-timeslice-is-an-unsigned-long-not-an-int
+++ a/drivers/parport/procfs.c
@@ -384,7 +384,7 @@ parport_device_sysctl_template = {
{
.procname = "timeslice",
.data = NULL,
- .maxlen = sizeof(int),
+ .maxlen = sizeof(unsigned long),
.mode = 0644,
.proc_handler = &proc_doulongvec_ms_jiffies_minmax,
.extra1 = (void*) &parport_min_timeslice_value,
_
Patches currently in -mm which might be from dada1@cosmosbay.com are
parport-dev-timeslice-is-an-unsigned-long-not-an-int.patch
git-net.patch
percpu-__percpu_alloc_mask-can-dynamically-size-percpu_data.patch
get-rid-of-nr_open-and-introduce-a-sysctl_nr_open.patch
reply other threads:[~2007-12-11 23:32 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=200712112331.lBBNV3SW014665@imap1.linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=dada1@cosmosbay.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mm-commits@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 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.