* i2c-xgene-slimpro.c : dma_buffer overrun
@ 2016-10-06 21:22 Phil Endecott
0 siblings, 0 replies; only message in thread
From: Phil Endecott @ 2016-10-06 21:22 UTC (permalink / raw)
To: linux-i2c; +Cc: Feng Kan
Dear Experts,
Can someone please have a look at this declaration in i2c-xgene-slimpro.c:
struct slimpro_i2c_dev {
struct i2c_adapter adapter;
struct device *dev;
struct mbox_chan *mbox_chan;
struct mbox_client mbox_client;
struct completion rd_complete;
u8 dma_buffer[I2C_SMBUS_BLOCK_MAX];
u32 *resp_msg;
};
It seems to me that the size of dma_buffer should be I2C_SMBUS_BLOCK_MAX+2,
to match this in uapi/linux/i2c.h:
union i2c_smbus_data {
__u8 byte;
__u16 word;
__u8 block[I2C_SMBUS_BLOCK_MAX + 2]; /* block[0] is used for length */
/* and one more for user-space compatibility */
};
My debugging shows that 33 is often passed as readlen to dma_map_single()
in slimpro_i2c_blkrd(). So either the buffer needs to be larger, or the
caller is misbehaving. Certainly increasing the size of dma_buffer by 2
fixes crashes that I have been seeing.
This is the first time I've ever looked at anything in the i2c system so
I may have completely misunderstood everything....
(If I'm right, is anyone aware of any static analysis method that should have
been able to detect this?)
Thanks, Phil.
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~2016-10-06 21:46 UTC | newest]
Thread overview: (only message) (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2016-10-06 21:22 i2c-xgene-slimpro.c : dma_buffer overrun Phil Endecott
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox