From: "J. R. Okajima" <hooanon05g@gmail.com>
To: Prasad Koya <prasad.koya@gmail.com>
Cc: linux-fsdevel@vger.kernel.org, aufs-users@lists.sourceforge.net
Subject: Re: aufs crash at au_set_fbstart in aufs3 (3.4 kernel).
Date: Tue, 17 Jul 2018 23:29:08 +0900 [thread overview]
Message-ID: <6716.1531837748@jrobl> (raw)
In-Reply-To: <CAGXD9OddA9JRuPuG88zEwwNkzt3Ouro0RcvbKvcvPSH69tox=g@mail.gmail.com>
Prasad Koya:
> > Has anyone run into this crash with aufs 3? We hit this in production.
:::
> > <1>[45257161.254682] BUG: unable to handle kernel NULL pointer
> > dereference at 0000000000000038
> > <1>[45257161.351193] IP: [<ffffffff8117a5dc>] au_do_open_nondir+0x3b/0xaf
I don't think it a good idea to post vger.kernel.org ML since aufs is
not mainlined. It is recommended to post aufs-users ML only, with these
info.
(from aufs README file)
----------------------------------------------------------------------
When you have any problems or strange behaviour in aufs, please let me
know with:
- /proc/mounts (instead of the output of mount(8))
- /sys/module/aufs/*
- /sys/fs/aufs/* (if you have them)
- /debug/aufs/* (if you have them)
- linux kernel version
if your kernel is not plain, for example modified by distributor,
the url where i can download its source is necessary too.
- aufs version which was printed at loading the module or booting the
system, instead of the date you downloaded.
- configuration (define/undefine CONFIG_AUFS_xxx)
- kernel configuration or /proc/config.gz (if you have it)
- behaviour which you think to be incorrect
- actual operation, reproducible one is better
- mailto: aufs-users at lists.sourceforge.net
----------------------------------------------------------------------
Last but not lease, as you surely know, aufs3.4 has been unsupported
since Nov 2013.
J. R. Okajima
next prev parent reply other threads:[~2018-07-17 15:02 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-16 21:29 aufs crash at au_set_fbstart in aufs3 (3.4 kernel) Prasad Koya
2018-07-16 21:30 ` Prasad Koya
2018-07-17 14:29 ` J. R. Okajima [this message]
2018-07-17 2:11 ` Matthew Wilcox
2018-07-17 2:46 ` Prasad Koya
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=6716.1531837748@jrobl \
--to=hooanon05g@gmail.com \
--cc=aufs-users@lists.sourceforge.net \
--cc=linux-fsdevel@vger.kernel.org \
--cc=prasad.koya@gmail.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