From: Sergey Senozhatsky <sergey.senozhatsky.work@gmail.com>
To: Naresh Kamboju <naresh.kamboju@linaro.org>
Cc: Al Viro <viro@zeniv.linux.org.uk>,
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: Wed, 26 Jul 2017 09:29:14 +0900 [thread overview]
Message-ID: <20170726002914.GA7471@jagdpanzerIV.localdomain> (raw)
In-Reply-To: <CA+G9fYvHEHk05OmrQ5ndbbkAo71FmpxTSLD_G=mjWOEujygtuQ@mail.gmail.com>
On (07/24/17 14:59), Naresh Kamboju wrote:
> 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
FYI,
https://patchwork.kernel.org/patch/9861253/
-ss
prev parent reply other threads:[~2017-07-26 0:29 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
2017-07-26 0:29 ` Sergey Senozhatsky [this message]
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=20170726002914.GA7471@jagdpanzerIV.localdomain \
--to=sergey.senozhatsky.work@gmail.com \
--cc=keescook@chromium.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=naresh.kamboju@linaro.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).