From: Jason Wang <hidden> Date: 2018-02-07 08:08:32
To avoid slab to warn about exceeded size, fail early if queue
occupies more than KMALLOC_MAX_SIZE.
Reported-by: syzbot+e4d4f9ddd4295539735d@syzkaller.appspotmail.com
Signed-off-by: Jason Wang <redacted>
---
include/linux/ptr_ring.h | 2 ++
1 file changed, 2 insertions(+)
From: Jason Wang <hidden> Date: 2018-02-07 09:18:08
On 2018年02月07日 16:08, Jason Wang wrote:
quoted hunk
To avoid slab to warn about exceeded size, fail early if queue
occupies more than KMALLOC_MAX_SIZE.
Reported-by: syzbot+e4d4f9ddd4295539735d@syzkaller.appspotmail.com
Signed-off-by: Jason Wang <redacted>
---
include/linux/ptr_ring.h | 2 ++
1 file changed, 2 insertions(+)
From: "Michael S. Tsirkin" <mst@redhat.com> Date: 2018-02-07 15:15:38
On Wed, Feb 07, 2018 at 05:17:59PM +0800, Jason Wang wrote:
On 2018年02月07日 16:08, Jason Wang wrote:
quoted
To avoid slab to warn about exceeded size, fail early if queue
occupies more than KMALLOC_MAX_SIZE.
Reported-by: syzbot+e4d4f9ddd4295539735d@syzkaller.appspotmail.com
Signed-off-by: Jason Wang <redacted>
---
include/linux/ptr_ring.h | 2 ++
1 file changed, 2 insertions(+)
@@ -466,6 +466,8 @@ static inline int ptr_ring_consume_batched_bh(struct ptr_ring *r,staticinlinevoid**__ptr_ring_init_queue_alloc(unsignedintsize,gfp_tgfp){+if(size>KMALLOC_MAX_SIZE)+returnNULL;returnkcalloc(size,sizeof(void*),gfp);}
Fixes: 2e0ab8ca83c12 ("ptr_ring: array based FIFO for pointers")
That's probably not enough. How about switching to kvmalloc and limiting
this drastically to e.g. 64K. I vaguely remember that some wise man said
that should be enough for everybody :)
--
MST
From: Jason Wang <hidden> Date: 2018-02-08 03:04:25
On 2018年02月07日 23:15, Michael S. Tsirkin wrote:
On Wed, Feb 07, 2018 at 05:17:59PM +0800, Jason Wang wrote:
quoted
On 2018年02月07日 16:08, Jason Wang wrote:
quoted
To avoid slab to warn about exceeded size, fail early if queue
occupies more than KMALLOC_MAX_SIZE.
Reported-by: syzbot+e4d4f9ddd4295539735d@syzkaller.appspotmail.com
Signed-off-by: Jason Wang <redacted>
---
include/linux/ptr_ring.h | 2 ++
1 file changed, 2 insertions(+)
@@ -466,6 +466,8 @@ static inline int ptr_ring_consume_batched_bh(struct ptr_ring *r,staticinlinevoid**__ptr_ring_init_queue_alloc(unsignedintsize,gfp_tgfp){+if(size>KMALLOC_MAX_SIZE)+returnNULL;returnkcalloc(size,sizeof(void*),gfp);}
Fixes: 2e0ab8ca83c12 ("ptr_ring: array based FIFO for pointers")
That's probably not enough. How about switching to kvmalloc and limiting
this drastically to e.g. 64K. I vaguely remember that some wise man said
that should be enough for everybody :)
Okay, let me post a V2 to see if there's any objection.
Thanks
From: "Michael S. Tsirkin" <mst@redhat.com> Date: 2018-02-08 15:44:51
On Wed, Feb 07, 2018 at 04:08:25PM +0800, Jason Wang wrote:
quoted hunk
To avoid slab to warn about exceeded size, fail early if queue
occupies more than KMALLOC_MAX_SIZE.
Reported-by: syzbot+e4d4f9ddd4295539735d@syzkaller.appspotmail.com
Signed-off-by: Jason Wang <redacted>
---
include/linux/ptr_ring.h | 2 ++
1 file changed, 2 insertions(+)
@@ -466,6 +466,8 @@ static inline int ptr_ring_consume_batched_bh(struct ptr_ring *r,staticinlinevoid**__ptr_ring_init_queue_alloc(unsignedintsize,gfp_tgfp){+if(size>KMALLOC_MAX_SIZE)+returnNULL;returnkcalloc(size,sizeof(void*),gfp);}
I guess this approach does begin to make more sense
at least as a temporary stop-gap.
But does this actually prevent the crash in all cases?
size is in void* entry units, KMALLOC_MAX_SIZE is in bytes.