All of lore.kernel.org
 help / color / mirror / Atom feed
From: Naresh Kamboju <naresh.kamboju@linaro.org>
To: Al Viro <viro@zeniv.linux.org.uk>
Cc: linux-fsdevel@vger.kernel.org,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	Kees Cook <keescook@chromium.org>
Subject: Re: Kernel BUG at fs/namei.c:248
Date: Mon, 24 Jul 2017 14:59:54 +0530	[thread overview]
Message-ID: <CA+G9fYvHEHk05OmrQ5ndbbkAo71FmpxTSLD_G=mjWOEujygtuQ@mail.gmail.com> (raw)
In-Reply-To: <CA+G9fYtnk2hsSM0iRfWJmt6=pUmEpaA7hd=4thbAqvgXu7Tc2w@mail.gmail.com>

This bug still occurring on linux-next : 4.13.0-rc2-next-20170724.

>>> [ 1245.412625] kernel BUG at
>>> /srv/oe/build/tmp-rpb-glibc/work-shared/hikey/kernel-source/fs/namei.c:248!
>>
>> Interesting... Looks like double-put or memory corruptor of some sort.
>> Nothing obvious jumps out at the first glance; I'll look into that when
>> I get back to better connectivity tonight.


[ 1233.512841] kernel BUG at
/srv/oe/build/tmp-rpb-glibc/work-shared/hikey/kernel-source/fs/namei.c:248!
zram load module [ 1233.522161] Internal error: Oops - BUG: 0 [#1] PREEMPT SMP
successful
set m[ 1233.529054] Modules linked in: zram lzo test_printf algif_hash
af_alg adv7511 kirin_drm drm_kms_helper dw_drm_dsi drm asix usbnet
fuse [last unloaded: zram]
[ 1233.544586] CPU: 0 PID: 14163 Comm: systemd-udevd Not tainted
4.13.0-rc2-next-20170724 #1


LAVA test job id,
https://lkft.validation.linaro.org/scheduler/job/15352#L3402

>
> I am able to reproduce this BUG by running zram test cases multiple
> times in a row.
> http://people.linaro.org/~naresh.kamboju/zram.tar.gz
>
> Ref:
> LKFT: linux-mainline: Kernel BUG at fs/namei.c:248
> https://bugs.linaro.org/show_bug.cgi?id=3140

  reply	other threads:[~2017-07-24  9:30 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-07-19 10:24 Kernel BUG at fs/namei.c:248 Naresh Kamboju
2017-07-19 13:54 ` Al Viro
2017-07-19 16:16   ` Naresh Kamboju
2017-07-24  9:29     ` Naresh Kamboju [this message]
2017-07-26  0:29       ` Sergey Senozhatsky

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CA+G9fYvHEHk05OmrQ5ndbbkAo71FmpxTSLD_G=mjWOEujygtuQ@mail.gmail.com' \
    --to=naresh.kamboju@linaro.org \
    --cc=keescook@chromium.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=viro@zeniv.linux.org.uk \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.