Re: [PATCH v3] vhost: avoid potential null pointer access

2023-09-25 Thread Maxime Coquelin
On 9/25/23 12:37, Morten Brørup wrote: From: Maxime Coquelin [mailto:maxime.coque...@redhat.com] Sent: Monday, 25 September 2023 10.15 On 9/12/23 09:42, Li Feng wrote: If the user calls rte_vhost_vring_call() on a ring that has been invalidated, we will encounter SEGV. We should check the p

RE: [PATCH v3] vhost: avoid potential null pointer access

2023-09-25 Thread Morten Brørup
> From: Maxime Coquelin [mailto:maxime.coque...@redhat.com] > Sent: Monday, 25 September 2023 10.15 > > On 9/12/23 09:42, Li Feng wrote: > > If the user calls rte_vhost_vring_call() on a ring that has been > > invalidated, we will encounter SEGV. > > > > We should check the pointer firstly before

Re: [PATCH v3] vhost: avoid potential null pointer access

2023-09-25 Thread Maxime Coquelin
On 9/25/23 10:15, Maxime Coquelin wrote: On 9/12/23 09:42, Li Feng wrote: If the user calls rte_vhost_vring_call() on a ring that has been invalidated, we will encounter SEGV. We should check the pointer firstly before accessing it. Signed-off-by: Li Feng --- v2 -> v3: - Also fix the rte

Re: [PATCH v3] vhost: avoid potential null pointer access

2023-09-25 Thread Maxime Coquelin
On 9/12/23 09:42, Li Feng wrote: If the user calls rte_vhost_vring_call() on a ring that has been invalidated, we will encounter SEGV. We should check the pointer firstly before accessing it. Signed-off-by: Li Feng --- v2 -> v3: - Also fix the rte_vhost_vring_call_nonblock. v1 -> v2: - Fix

[PATCH v3] vhost: avoid potential null pointer access

2023-09-12 Thread Li Feng
If the user calls rte_vhost_vring_call() on a ring that has been invalidated, we will encounter SEGV. We should check the pointer firstly before accessing it. Signed-off-by: Li Feng --- v2 -> v3: - Also fix the rte_vhost_vring_call_nonblock. v1 -> v2: - Fix rebase error. lib/vhost/vhost.c |