Workaround Linux AMD driver bug where TEXTURE_MAX_ANISOTROPY init value is incorrect.

gpu/command_buffer/service/texture_manager.h

Index: gpu/command_buffer/service/texture_manager.h
diff --git a/gpu/command_buffer/service/texture_manager.h b/gpu/command_buffer/service/texture_manager.h
index c44bef314af061d29d6ea5b0c8b177db0ba10631..2682e466d6c2ca4c86dd07c019d494274e0bf3a2 100644
--- a/gpu/command_buffer/service/texture_manager.h
+++ b/gpu/command_buffer/service/texture_manager.h
@@ -159,6 +159,9 @@ class GPU_EXPORT Texture {
     return estimated_size() > 0;
   }
 
+  // Initialize TEXTURE_MAX_ANISOTROPY to 1 if we haven't done so yet.
+  void InitTextureMaxAnisotropyIfNeeded(GLenum target);
+
  private:
   friend class MailboxManager;
   friend class MailboxManagerTest;
@@ -379,6 +382,9 @@ class GPU_EXPORT Texture {
   // Cache of the computed CanRenderCondition flag.
   CanRenderCondition can_render_condition_;
 
+  // Whether we have initialized TEXTURE_MAX_ANISOTROPY to 1.
+  bool texture_max_anisotropy_initialized_;
+
   DISALLOW_COPY_AND_ASSIGN(Texture);
 };