From: Dave <kilroyd@googlemail.com>
To: Andrey Borzenkov <arvidjaar@mail.ru>
Cc: orinoco-devel@lists.sourceforge.net, linux-wireless@vger.kernel.org
Subject: Re: [Orinoco-devel] [PATCH 1/2] orinoco: validate firmware header
Date: Fri, 20 Feb 2009 19:19:13 +0000 [thread overview]
Message-ID: <499F0231.5080103@gmail.com> (raw)
In-Reply-To: <200902202126.12230.arvidjaar@mail.ru>
Andrey Borzenkov wrote:
> On 20 of February 2009 02:46:26 David Kilroy wrote:
>> +static const char *fw_err[] = {
>> + "image too small",
>> +};
>> +
>>
>> +/* Check the range of various header entries */
>> +static int validate_fw(const struct orinoco_fw_header *hdr, size_t
>> len) +{
>> + if (len < sizeof(*hdr))
>> + return 1;
>> +
>> + /* TODO: consider adding a checksum or CRC to the firmware format
>> */ + return 0;
>> +}
>
>
> I am afraid this can easily go off sync. Any reason those messages
> cannot be printed inline in validate_fw()?
That's how I started, but I didn't like having to pass down struct
net_device/struct orinoco_private just to print an error.
> Otherwise what about
>
> #define FW_ERR_OK 0
> #define FW_ERR_TOO_SMALL 1
> ...
> static const char *fw_err[] = {
> [FW_ERR_TOO_SMALL] = "image too small",
> ?
Sure. That (or an enumeration) documents the error codes. A little
tedious though. What if I did something like:
static char * validate_fw(...)
{
if (len < sizeof(*hdr))
return "image too small";
...
return NULL;
}
...
{
char *fw_err = validate_firmware(hdr, fw_entry->size);
if (fw_err != NULL) {
printk(KERN_WARNING "%s: Invalid firmware (%s)\n",
dev->name, fw_err)
err = -EINVAL;
goto abort;
}
}
Dave.
next prev parent reply other threads:[~2009-02-20 19:19 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-19 23:46 [PATCH 0/2] orinoco: improve robustness of firmware load David Kilroy
2009-02-19 23:46 ` [PATCH 1/2] orinoco: validate firmware header David Kilroy
2009-02-20 18:26 ` [Orinoco-devel] " Andrey Borzenkov
2009-02-20 19:19 ` Dave [this message]
2009-02-19 23:46 ` [PATCH 2/2] orinoco: prevent accessing memory outside the firmware image David Kilroy
2009-02-20 19:28 ` Dave
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=499F0231.5080103@gmail.com \
--to=kilroyd@googlemail.com \
--cc=arvidjaar@mail.ru \
--cc=linux-wireless@vger.kernel.org \
--cc=orinoco-devel@lists.sourceforge.net \
/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;
as well as URLs for NNTP newsgroup(s).