commit | 40d992cc0f7356f179b31ae71473538e0e09fd97 | [log] [tgz] |
---|---|---|
author | Wade Guthrie <wdg@chromium.org> | Fri Apr 19 11:10:11 2013 -0700 |
committer | ChromeBot <chrome-bot@google.com> | Tue May 21 16:15:26 2013 -0700 |
tree | 3225245126c29c81300050aee452edc7a290e6c8 | |
parent | 8f6479fed67969c162aa079eed04c55ee574a841 [diff] |
shill: Makes unknown nl80211 messages look like Nl80211Messages. Before, when NetlinkMessage::CreateMessage was given an nl80211 message that it didn't recognize, the code generated something that was a sort-of hybrid between a vanilla NetlinkMessage and an Nl80211Message (with disasterous results). This makes the unknown message look just like an Nl80211Message. The specific problem this addresses happened because a developer added a new message type but hadn't, yet, added it to the factory. This generated an UnknownMessage and passed it to the message handler. BUG=None TEST=unitest Change-Id: I78bc0861725c660f794c9eec2b99d23dded7d7a2 Reviewed-on: https://gerrit.chromium.org/gerrit/50525 Commit-Queue: Wade Guthrie <wdg@chromium.org> Reviewed-by: Wade Guthrie <wdg@chromium.org> Tested-by: Wade Guthrie <wdg@chromium.org>