Patch "drm/i915: Prevent zero length "index" write" has been added to the 4.4-stable tree
Subsystems (3)
This is a note to let you know that I've just added the patch titled
drm/i915: Prevent zero length "index" write
to the 4.4-stable tree which can be found at:
http://www.kernel.org/git/?p=linux/kernel/git/stable/stable-queue.git;a=summary
The filename of the patch is:
drm-i915-prevent-zero-length-index-write.patch
and it can be found in the queue-4.4 subdirectory.
If you, or anyone else, feels it should not be added to the stable tree, please let <[email protected]> know about it.
Quoted 1 line
From
56350fb8978bbf4aafe08f21234e161dd128b417Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Ville=20Syrj=C3=A4l=C3=A4?= <[email protected]>
Date: Thu, 23 Nov 2017 21:41:57 +0200
Subject: drm/i915: Prevent zero length "index" write
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit
From: Ville Syrjälä <[email protected]>
commit 56350fb8978bbf4aafe08f21234e161dd128b417 upstream.
The hardware always writes one or two bytes in the index portion of an indexed transfer. Make sure the message we send as the index doesn't have a zero length.
--- drivers/gpu/drm/i915/intel_i2c.c | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-)
drivers/gpu/drm/i915/intel_i2c.c +2 -1
@@ -441,7 +441,8 @@ gmbus_is_index_read(struct i2c_msg *msgs {return (i +1 < num && msgs[i].addr == msgs[i +1 ].addr && - !(msgs[i].flags &I2C_M_RD ) && msgs[i].len <=2 && + !(msgs[i].flags &I2C_M_RD ) && + (msgs[i].len ==1 || msgs[i].len ==2 ) && (msgs[i +1 ].flags &I2C_M_RD )); }
Patches currently in stable-queue which might be from [email protected] are
queue-4.4/drm-i915-prevent-zero-length-index-write.patch queue-4.4/drm-i915-don-t-try-indexed-reads-to-alternate-slave-addresses.patch