Hi Progyan, On Thu, 15 Feb 2018 10:04:18 +0530 Progyan Bhattacharya <bprogyan@xxxxxxxxx> wrote: > > I did some ground work and found this particular commit that causing the > error. > > Commit Hash: d96977a8c2266792397ed9814bb84b5129a278ad That hash does not appear in linux-next (or Linus' tree). > Commit Body: > > kasan: rework Kconfig settings > > We get a lot of very large stack frames using gcc-7.0.1 with the default > -fsanitize-address-use-after-scope --param asan-stack=1 options, which can > easily cause an overflow of the kernel stack, e.g.... > > Author(s): > > Signed-off-by: Arnd Bergmann <arnd@xxxxxxxx> > Acked-by: Andrey Ryabinin <aryabinin@xxxxxxxxxxxxx> > Cc: Mauro Carvalho Chehab <mchehab@xxxxxxxxxx> > Cc: Andrey Ryabinin <aryabinin@xxxxxxxxxxxxx> > Cc: Alexander Potapenko <glider@xxxxxxxxxx> > Cc: Dmitry Vyukov <dvyukov@xxxxxxxxxx> > Cc: Andrey Konovalov <andreyknvl@xxxxxxxxxx> > Cc: <stable@xxxxxxxxxxxxxxx> > Signed-off-by: Andrew Morton <akpm@xxxxxxxxxxxxxxxxxxxx> > Signed-off-by: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx> That patch is in Linus' tree now (was in linux-next) but has SHA1 e7c52b84fb18 -- Cheers, Stephen Rothwell -- To unsubscribe from this list: send the line "unsubscribe linux-next" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html