Re: [PATCH 2/2] cifs: Allocate memory for all iovs in smb2_ioctl

2019-05-15 Thread Steve French
merged into cifs-2.6.git for-next On Wed, May 15, 2019 at 4:10 PM wrote: > > From: Long Li > > An IOCTL uses up to 2 iovs. The 1st iov is the command itself, the 2nd iov is > optional data for that command. The 1st iov is always allocated on the heap > but the 2nd iov may point to a variable on

Re: [PATCH 2/2] cifs: Allocate memory for all iovs in smb2_ioctl

2019-05-15 Thread ronnie sahlberg
On Thu, May 16, 2019 at 7:10 AM wrote: > > From: Long Li > > An IOCTL uses up to 2 iovs. The 1st iov is the command itself, the 2nd iov is > optional data for that command. The 1st iov is always allocated on the heap > but the 2nd iov may point to a variable on the stack. This will trigger an >

Re: [PATCH 2/2] cifs: Allocate memory for all iovs in smb2_ioctl

2019-05-15 Thread Pavel Shilovsky
ср, 15 мая 2019 г. в 14:10, : > > From: Long Li > > An IOCTL uses up to 2 iovs. The 1st iov is the command itself, the 2nd iov is > optional data for that command. The 1st iov is always allocated on the heap > but the 2nd iov may point to a variable on the stack. This will trigger an > error when

[PATCH 2/2] cifs: Allocate memory for all iovs in smb2_ioctl

2019-05-15 Thread longli
From: Long Li An IOCTL uses up to 2 iovs. The 1st iov is the command itself, the 2nd iov is optional data for that command. The 1st iov is always allocated on the heap but the 2nd iov may point to a variable on the stack. This will trigger an error when passing the 2nd iov for RDMA I/O. Fix