Yes -- this is a follow-up investigation into how that bug might have occurred by looking at recent commits to AOSP.