Re: [PATCH] rpmsg: glink: use only lower 16-bits of param2 for CMD_OPEN name length

2024-10-07 Thread Dmitry Baryshkov
On Mon, Oct 07, 2024 at 09:19:05AM GMT, Jonathan Marek wrote: > On 10/7/24 9:16 AM, Dmitry Baryshkov wrote: > > On Mon, Oct 07, 2024 at 12:47:22AM GMT, Jonathan Marek wrote: > > > The name len field of the CMD_OPEN packet is only 16-bits and the upper > > > 16-bits of "param2" are a different field

Re: [PATCH] rpmsg: glink: use only lower 16-bits of param2 for CMD_OPEN name length

2024-10-07 Thread Jonathan Marek
On 10/7/24 9:16 AM, Dmitry Baryshkov wrote: On Mon, Oct 07, 2024 at 12:47:22AM GMT, Jonathan Marek wrote: The name len field of the CMD_OPEN packet is only 16-bits and the upper 16-bits of "param2" are a different field, which can be nonzero in certain situations, and CMD_OPEN packets can be une

Re: [PATCH] rpmsg: glink: use only lower 16-bits of param2 for CMD_OPEN name length

2024-10-07 Thread Dmitry Baryshkov
On Mon, Oct 07, 2024 at 12:47:22AM GMT, Jonathan Marek wrote: > The name len field of the CMD_OPEN packet is only 16-bits and the upper > 16-bits of "param2" are a different field, which can be nonzero in certain > situations, and CMD_OPEN packets can be unexpectedly dropped because of > this. Any

[PATCH] rpmsg: glink: use only lower 16-bits of param2 for CMD_OPEN name length

2024-10-06 Thread Jonathan Marek
The name len field of the CMD_OPEN packet is only 16-bits and the upper 16-bits of "param2" are a different field, which can be nonzero in certain situations, and CMD_OPEN packets can be unexpectedly dropped because of this. Fix this by masking out the upper 16 bits of param2. (the commit in this