From: akpm@linux-foundation.org
To: mm-commits@vger.kernel.org
Cc: steven@strobe.cc, greg@kroah.com, stable@kernel.org
Subject: + drivers-usb-mon-mon_binc-resizing-usbmon-binary-interface-buffer-causes-protection-faults.patch added to -mm tree
Date: Thu, 22 Jul 2010 15:56:13 -0700 [thread overview]
Message-ID: <201007222256.o6MMuDP5016969@imap1.linux-foundation.org> (raw)
The patch titled
drivers/usb/mon/mon_bin.c: resizing usbmon binary interface buffer causes protection faults
has been added to the -mm tree. Its filename is
drivers-usb-mon-mon_binc-resizing-usbmon-binary-interface-buffer-causes-protection-faults.patch
Before you just go and hit "reply", please:
a) Consider who else should be cc'ed
b) Prefer to cc a suitable mailing list as well
c) Ideally: find the original patch on the mailing list and do a
reply-to-all to that, adding suitable additional cc's
*** Remember to use Documentation/SubmitChecklist when testing your code ***
See http://userweb.kernel.org/~akpm/stuff/added-to-mm.txt to find
out what to do about this
The current -mm tree may be found at http://userweb.kernel.org/~akpm/mmotm/
------------------------------------------------------
Subject: drivers/usb/mon/mon_bin.c: resizing usbmon binary interface buffer causes protection faults
From: Steven Robertson <steven@strobe.cc>
Enlarging the buffer size via the MON_IOCT_RING_SIZE ioctl causes general
protection faults. It appears the culprit is an incorrect argument to
mon_free_buff: instead of passing the size of the current buffer being
freed, the size of the new buffer is passed.
Use the correct size argument to mon_free_buff when changing the size of
the buffer.
Signed-off-by: Steven Robertson <steven@strobe.cc>
Cc: Greg KH <greg@kroah.com>
Cc: <stable@kernel.org>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
---
drivers/usb/mon/mon_bin.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff -puN drivers/usb/mon/mon_bin.c~drivers-usb-mon-mon_binc-resizing-usbmon-binary-interface-buffer-causes-protection-faults drivers/usb/mon/mon_bin.c
--- a/drivers/usb/mon/mon_bin.c~drivers-usb-mon-mon_binc-resizing-usbmon-binary-interface-buffer-causes-protection-faults
+++ a/drivers/usb/mon/mon_bin.c
@@ -1004,7 +1004,7 @@ static long mon_bin_ioctl(struct file *f
mutex_lock(&rp->fetch_lock);
spin_lock_irqsave(&rp->b_lock, flags);
- mon_free_buff(rp->b_vec, size/CHUNK_SIZE);
+ mon_free_buff(rp->b_vec, rp->b_size/CHUNK_SIZE);
kfree(rp->b_vec);
rp->b_vec = vec;
rp->b_size = size;
_
Patches currently in -mm which might be from steven@strobe.cc are
drivers-usb-mon-mon_binc-resizing-usbmon-binary-interface-buffer-causes-protection-faults.patch
reply other threads:[~2010-07-22 22:56 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=201007222256.o6MMuDP5016969@imap1.linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mm-commits@vger.kernel.org \
--cc=stable@kernel.org \
--cc=steven@strobe.cc \
/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