Re: "lib: rework bitmap_parse()" triggers invalid access errors

2019-06-06 Thread Yury Norov
On Thu, Jun 06, 2019 at 12:09:46PM -0400, Qian Cai wrote: > On Wed, 2019-06-05 at 08:01 +, Yuri Norov wrote: > > (Sorry for top-posting) > > > > I can reproduce this on next-20190604. Is it new trace, or like one you've > > posted before? > > Same thing, "nbits" causes an invalid access. > >

Re: "lib: rework bitmap_parse()" triggers invalid access errors

2019-06-06 Thread Qian Cai
On Wed, 2019-06-05 at 08:01 +, Yuri Norov wrote: > (Sorry for top-posting) > > I can reproduce this on next-20190604. Is it new trace, or like one you've > posted before? Same thing, "nbits" causes an invalid access. # ./scripts/faddr2line vmlinux bitmap_parse+0x20c/0x2d8 bitmap_parse+0x20c/

Re: "lib: rework bitmap_parse()" triggers invalid access errors

2019-06-04 Thread Qian Cai
BTW, this problem below is still reproducible after applied the series [1] on the top of today's linux-next tree "next-20190604" which has already included the patch for the "Bad swap file entry" issue. [1] https://lore.kernel.org/lkml/20190501010636.30595-1-yno...@marvell.com/ On Thu, 2019-05-30

"lib: rework bitmap_parse()" triggers invalid access errors

2019-05-30 Thread Qian Cai
The linux-next commit "lib: rework bitmap_parse" triggers errors below during boot on both arm64 and powerpc with KASAN_SW_TAGS or SLUB_DEBUG enabled. Reverted the commit and its dependency (lib: opencode in_str()) fixed the issue. [   67.056867][ T3737] BUG kmalloc-16 (Tainted: GB