From: "Justin Mattock" <justinmattock@gmail.com>
To: "Johannes Weiner" <hannes@saeurebad.de>
Cc: "Matthew Garrett" <mjg59@srcf.ucam.org>,
"Andrew Morton" <akpm@linux-foundation.org>,
greg@kroah.com, linux-kernel@vger.kernel.org,
linux-usb@vger.kernel.org
Subject: Re: [PATCH] isight_firmware: Avoid crash on loading invalid firmware
Date: Sat, 7 Jun 2008 02:38:56 +0000 [thread overview]
Message-ID: <dd18b0c30806061938g95cfafbm69804bb38c13ed74@mail.gmail.com> (raw)
In-Reply-To: <873anq5a2b.fsf@saeurebad.de>
On Sat, Jun 7, 2008 at 1:05 AM, Johannes Weiner <hannes@saeurebad.de> wrote:
> Matthew Garrett <mjg59@srcf.ucam.org> writes:
>
>> 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
>> preseent. Fixes crash reported by Justin Mattock.
>
> You don't like the word `present', do you? ;)
>
> Hannes
>
pre seent meaning sent ahead of time,
or present as in time now, right on the spot. as for the word present
for liking +"I guess the kind at christmas time" : -)
regards;
--
Justin P. Mattock
prev parent reply other threads:[~2008-06-07 2:39 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
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 [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=dd18b0c30806061938g95cfafbm69804bb38c13ed74@mail.gmail.com \
--to=justinmattock@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=greg@kroah.com \
--cc=hannes@saeurebad.de \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®