[RESTRICT AUTOMERGE]: CTS test fix for Android Security CVE-2017-0665

For some reason mCore->mConsumerName.mString can be null on some partner
devices. This causes a segmentation fault and false positive test
failure.

Bug: 72385489
Bug: 36991414
Test: cts-tradefed run cts -m CtsSecurityBulletinHostTestCases -t android.security.cts.Poc17_07#testPocBug_36991414
Change-Id: I2e61ba4485dfb1c39b07bc1961f805e4b522b58a
diff --git a/hostsidetests/securitybulletin/securityPatch/Bug-36991414/BufferQueueProducer.cpp b/hostsidetests/securitybulletin/securityPatch/Bug-36991414/BufferQueueProducer.cpp
index e39a3cc..f63df4c 100644
--- a/hostsidetests/securitybulletin/securityPatch/Bug-36991414/BufferQueueProducer.cpp
+++ b/hostsidetests/securitybulletin/securityPatch/Bug-36991414/BufferQueueProducer.cpp
@@ -897,7 +897,6 @@
                                           QueueBufferOutput* output) {
   ATRACE_CALL();
   Mutex::Autolock lock(mCore->mMutex);
-  mConsumerName = mCore->mConsumerName;
   BQ_LOGV("connect: api=%d producerControlledByApp=%s", api,
           producerControlledByApp ? "true" : "false");