From: Sergey Senozhatsky <sergey.senozhatsky.work@gmail.com>
To: Junxiao Bi <junxiao.bi@oracle.com>
Cc: linux-next@vger.kernel.org,
"ocfs2-devel@oss.oracle.com" <ocfs2-devel@oss.oracle.com>,
Devel FS Linux <linux-fsdevel@vger.kernel.org>,
Linux Kernel mailing list <linux-kernel@vger.kernel.org>
Subject: Re: kernel panic on next-20160225
Date: Fri, 26 Feb 2016 17:05:06 +0900 [thread overview]
Message-ID: <20160226080506.GB509@swordfish> (raw)
In-Reply-To: <56CFF19E.4010003@oracle.com>
On (02/26/16 14:33), Junxiao Bi wrote:
> Hi,
>
> The following panic is triggered when run ocfs2 xattr test on
> linux-next-20160225. Did anybody ever see this?
>
perhaps "fs: NULL deref in atime_needs_update"
http://marc.info/?i=CACT4Y+ae=DQjrTtwSqm1PJ9rsnRAvKiBkRjBqaQH6f6W1dOh2Q@mail.gmail.com
-ss
prev parent reply other threads:[~2016-02-26 8:03 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-26 6:33 kernel panic on next-20160225 Junxiao Bi
2016-02-26 8:05 ` 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=20160226080506.GB509@swordfish \
--to=sergey.senozhatsky.work@gmail.com \
--cc=junxiao.bi@oracle.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=ocfs2-devel@oss.oracle.com \
/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).