All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@linux-foundation.org>
To: Matthew Garrett <mjg59@srcf.ucam.org>
Cc: greg@kroah.com, justinmattock@gmail.com,
	linux-kernel@vger.kernel.org, linux-usb@vger.kernel.org
Subject: Re: [PATCH] isight_firmware: Avoid crash on loading invalid firmware
Date: Fri, 6 Jun 2008 12:35:11 -0700	[thread overview]
Message-ID: <20080606123511.38ffbdde.akpm@linux-foundation.org> (raw)
In-Reply-To: <20080606192135.GA16727@srcf.ucam.org>

On Fri, 6 Jun 2008 20:21:35 +0100
Matthew Garrett <mjg59@srcf.ucam.org> wrote:

> Different tools generate slightly different formats of the isight 
> firmware. Ensure that the firmware buffer is not overrun, while still 
> ensuring that the correct amount of data is written if trailing data is 
> prseent.

It would have been nice to have mentioned this Justin Maddock fellow
in the changelog.


  reply	other threads:[~2008-06-06 19:35 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-06-04 19:13 [ 88.628451] BUG: unable to handle kernel paging request at f8dbf000 "isight_firmware" Justin Mattock
2008-06-06  7:26 ` Andrew Morton
2008-06-06  8:37   ` Justin Mattock
2008-06-06 12:11     ` Matthew Garrett
2008-06-06 14:24       ` Justin Mattock
2008-06-06 18:07       ` Andrew Morton
2008-06-06 18:10         ` Justin Mattock
2008-06-06 18:38           ` Justin Mattock
2008-06-06 18:55             ` Greg KH
2008-06-06 19:21               ` [PATCH] isight_firmware: Avoid crash on loading invalid firmware Matthew Garrett
2008-06-06 19:35                 ` Andrew Morton [this message]
2008-06-06 19:48                   ` Matthew Garrett
2008-06-06 21:14                     ` Justin Mattock
2008-06-06 21:50                       ` Matthew Garrett
2008-06-06 22:20                         ` Justin Mattock
2008-06-07  1:05                     ` Johannes Weiner
2008-06-07  2:38                       ` Justin Mattock

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=20080606123511.38ffbdde.akpm@linux-foundation.org \
    --to=akpm@linux-foundation.org \
    --cc=greg@kroah.com \
    --cc=justinmattock@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=mjg59@srcf.ucam.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.