Closed Bug 888803 Opened 12 years ago Closed 12 years ago

Fix stagefright blocklisting to use case insensitive substring match

Categories

(Core :: Audio/Video, defect)

ARM
Android
defect
Not set
normal

Tracking

()

RESOLVED INVALID

People

(Reporter: cajbir, Assigned: cajbir)

Details

Attachments

(1 obsolete file)

The Stagefright blocklist code uses case insensitive exact match in places whereas it should use case insensitive substring matching. Recent additions to the blocklist have done this using the Find method and we should convert all other uses to this.
Assignee: nobody → chris.double
Status: NEW → ASSIGNED
Attachment #769581 - Flags: review?(bjacob)
Comment on attachment 769581 [details] [diff] [review] Change stagefright blocklist to use substring matching Review of attachment 769581 [details] [diff] [review]: ----------------------------------------------------------------- ::: widget/android/GfxInfo.cpp @@ +349,5 @@ > NS_LossyConvertUTF16toASCII cManufacturer(mManufacturer); > NS_LossyConvertUTF16toASCII cModel(mModel); > NS_LossyConvertUTF16toASCII cHardware(mHardware); > > + if (cHardware.Find("antares", true) != -1 || This _was_ case-sensitive. The new code is case-insensitive. Is this intentional? @@ +352,5 @@ > > + if (cHardware.Find("antares", true) != -1 || > + cHardware.Find("harmony", true) != -1 || > + cHardware.Find("picasso", true) != -1 || > + cHardware.Find("picasso_e", true) != -1 || picasso being a substring of picasso_e, this is now redundant. So at this point I need to ask, are you sure that a sweeping change like this, making it match substrings in all blacklist rules, is what you want?
I'm leaving for a 2-week vacation now, and I don't feel comfortable r+ing this at this point given my questions in comment 2. I suggest switching to Joe as reviewer here.
Attachment #769581 - Flags: review?(bjacob)
Attachment #769581 - Attachment is obsolete: true
(In reply to Benoit Jacob [:bjacob] (On vacation, be back on july 18) from comment #2) > So at this point I need to ask, are you sure that a sweeping change like > this, making it match substrings in all blacklist rules, is what you want? Thanks, on further thought I think you're right. We'll make changes as needed in future patches. Thanks for the sanity check!
Status: ASSIGNED → RESOLVED
Closed: 12 years ago
Resolution: --- → INVALID
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: