From: Jeff Garzik <jeff@garzik.org>
To: Kees Cook <kees@ubuntu.com>
Cc: linux-kernel@vger.kernel.org, Ben Collins <bcollins@ubuntu.com>
Subject: Re: [PATCHv2] misc: fix unterminated *_device_id lists
Date: Thu, 13 Sep 2007 01:09:06 -0400 [thread overview]
Message-ID: <46E8C5F2.4080009@garzik.org> (raw)
In-Reply-To: <20070913044504.GP8183@outflux.net>
Kees Cook wrote:
> Fixes drivers that do not correctly terminate their *_device_id lists.
> This results in garbage being spewed into modules.pcimap when the module
> happens to not have 28 NULL bytes following the table, and/or the last PCI
> ID is actually truncated from the table when calculating the modules.alias
> PCI aliases, causing those unfortunate device IDs to not auto-load.
>
> Signed-off-by: Kees Cook <kees@ubuntu.com>
> ---
> Re-send, using recommended list termination code-style.
> Diff is against 2.6.23-rc6.
ACK
prev parent reply other threads:[~2007-09-13 5:09 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-13 0:47 [PATCH] usb: fix unterminated usn_device_id lists Kees Cook
2007-09-13 1:15 ` Jeff Garzik
2007-09-13 3:54 ` Kees Cook
2007-09-13 4:02 ` Jeff Garzik
2007-09-13 4:45 ` [PATCHv2] misc: fix unterminated *_device_id lists Kees Cook
2007-09-13 5:09 ` Jeff Garzik [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=46E8C5F2.4080009@garzik.org \
--to=jeff@garzik.org \
--cc=bcollins@ubuntu.com \
--cc=kees@ubuntu.com \
--cc=linux-kernel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox