Re: [PATCH 09/12] i2c: qup: fix buffer overflow for multiple msg of maximum xfer len

2018-03-12 Thread Abhishek Sahu
On 2018-02-28 03:36, Christ, Austin wrote: Hey Abhishek, On 2/3/2018 12:58 AM, Abhishek Sahu wrote: The BAM mode requires buffer for start tag data and tx, rx SG list. Currently, this is being taken for maximum transfer length (65K). But an I2C transfer can have multiple messages and each

Re: [PATCH 09/12] i2c: qup: fix buffer overflow for multiple msg of maximum xfer len

2018-03-12 Thread Abhishek Sahu
On 2018-02-28 03:36, Christ, Austin wrote: Hey Abhishek, On 2/3/2018 12:58 AM, Abhishek Sahu wrote: The BAM mode requires buffer for start tag data and tx, rx SG list. Currently, this is being taken for maximum transfer length (65K). But an I2C transfer can have multiple messages and each

Re: [PATCH 09/12] i2c: qup: fix buffer overflow for multiple msg of maximum xfer len

2018-03-12 Thread Abhishek Sahu
On 2018-02-28 04:45, Andy Gross wrote: On Sat, Feb 03, 2018 at 01:28:14PM +0530, Abhishek Sahu wrote: The BAM mode requires buffer for start tag data and tx, rx SG list. Currently, this is being taken for maximum transfer length (65K). But an I2C transfer can have multiple messages and each

Re: [PATCH 09/12] i2c: qup: fix buffer overflow for multiple msg of maximum xfer len

2018-03-12 Thread Abhishek Sahu
On 2018-02-28 04:45, Andy Gross wrote: On Sat, Feb 03, 2018 at 01:28:14PM +0530, Abhishek Sahu wrote: The BAM mode requires buffer for start tag data and tx, rx SG list. Currently, this is being taken for maximum transfer length (65K). But an I2C transfer can have multiple messages and each

Re: [PATCH 09/12] i2c: qup: fix buffer overflow for multiple msg of maximum xfer len

2018-02-27 Thread Andy Gross
On Sat, Feb 03, 2018 at 01:28:14PM +0530, Abhishek Sahu wrote: > The BAM mode requires buffer for start tag data and tx, rx SG > list. Currently, this is being taken for maximum transfer length > (65K). But an I2C transfer can have multiple messages and each > message can be of this maximum length

Re: [PATCH 09/12] i2c: qup: fix buffer overflow for multiple msg of maximum xfer len

2018-02-27 Thread Andy Gross
On Sat, Feb 03, 2018 at 01:28:14PM +0530, Abhishek Sahu wrote: > The BAM mode requires buffer for start tag data and tx, rx SG > list. Currently, this is being taken for maximum transfer length > (65K). But an I2C transfer can have multiple messages and each > message can be of this maximum length

Re: [PATCH 09/12] i2c: qup: fix buffer overflow for multiple msg of maximum xfer len

2018-02-27 Thread Christ, Austin
Hey Abhishek, On 2/3/2018 12:58 AM, Abhishek Sahu wrote: The BAM mode requires buffer for start tag data and tx, rx SG list. Currently, this is being taken for maximum transfer length (65K). But an I2C transfer can have multiple messages and each message can be of this maximum length so the

Re: [PATCH 09/12] i2c: qup: fix buffer overflow for multiple msg of maximum xfer len

2018-02-27 Thread Christ, Austin
Hey Abhishek, On 2/3/2018 12:58 AM, Abhishek Sahu wrote: The BAM mode requires buffer for start tag data and tx, rx SG list. Currently, this is being taken for maximum transfer length (65K). But an I2C transfer can have multiple messages and each message can be of this maximum length so the

Re: [PATCH 09/12] i2c: qup: fix buffer overflow for multiple msg of maximum xfer len

2018-02-19 Thread Abhishek Sahu
On 2018-02-16 10:51, Sricharan R wrote: Hi Abhishek, On 2/3/2018 1:28 PM, Abhishek Sahu wrote: The BAM mode requires buffer for start tag data and tx, rx SG list. Currently, this is being taken for maximum transfer length (65K). But an I2C transfer can have multiple messages and each message

Re: [PATCH 09/12] i2c: qup: fix buffer overflow for multiple msg of maximum xfer len

2018-02-19 Thread Abhishek Sahu
On 2018-02-16 10:51, Sricharan R wrote: Hi Abhishek, On 2/3/2018 1:28 PM, Abhishek Sahu wrote: The BAM mode requires buffer for start tag data and tx, rx SG list. Currently, this is being taken for maximum transfer length (65K). But an I2C transfer can have multiple messages and each message

Re: [PATCH 09/12] i2c: qup: fix buffer overflow for multiple msg of maximum xfer len

2018-02-15 Thread Sricharan R
Hi Abhishek, On 2/3/2018 1:28 PM, Abhishek Sahu wrote: > The BAM mode requires buffer for start tag data and tx, rx SG > list. Currently, this is being taken for maximum transfer length > (65K). But an I2C transfer can have multiple messages and each > message can be of this maximum length so the

Re: [PATCH 09/12] i2c: qup: fix buffer overflow for multiple msg of maximum xfer len

2018-02-15 Thread Sricharan R
Hi Abhishek, On 2/3/2018 1:28 PM, Abhishek Sahu wrote: > The BAM mode requires buffer for start tag data and tx, rx SG > list. Currently, this is being taken for maximum transfer length > (65K). But an I2C transfer can have multiple messages and each > message can be of this maximum length so the

[PATCH 09/12] i2c: qup: fix buffer overflow for multiple msg of maximum xfer len

2018-02-03 Thread Abhishek Sahu
The BAM mode requires buffer for start tag data and tx, rx SG list. Currently, this is being taken for maximum transfer length (65K). But an I2C transfer can have multiple messages and each message can be of this maximum length so the buffer overflow will happen in this case. Since increasing

[PATCH 09/12] i2c: qup: fix buffer overflow for multiple msg of maximum xfer len

2018-02-03 Thread Abhishek Sahu
The BAM mode requires buffer for start tag data and tx, rx SG list. Currently, this is being taken for maximum transfer length (65K). But an I2C transfer can have multiple messages and each message can be of this maximum length so the buffer overflow will happen in this case. Since increasing