From: Richard Weinberger <richard@nod.at>
To: Han Xu <xhnjupt@gmail.com>
Cc: "linux-mtd@lists.infradead.org" <linux-mtd@lists.infradead.org>
Subject: Re: UBIFS Dump Stack on Android
Date: Fri, 4 Mar 2016 20:20:14 +0100 [thread overview]
Message-ID: <56D9DFEE.7040106@nod.at> (raw)
In-Reply-To: <CA+EcR23cFb_cY=CAHGcpaq9P9KU2mTDXbTh-OiuK3Oq_o3idDA@mail.gmail.com>
Han,
Am 04.03.2016 um 03:21 schrieb Han Xu:
> Hi Richard,
>
> We found an issue on Kernel 4.1 when running Android on UBIFS. Android
> required to enable SELINUX and exposed the issue, one ubifs_assert()
> function failed and caused dump stack.
>
> --- a/fs/ubifs/xattr.c
> +++ b/fs/ubifs/xattr.c
> @@ -309,7 +309,6 @@ static int setxattr(struct inode *host, const char
> *name, const void *value,
> union ubifs_key key;
> int err, type;
>
> ubifs_assert(mutex_is_locked(&host->i_mutex));
>
> It may related to your recent code change
> UBIFS: Kill unneeded locking in ubifs_init_security
>
> We also noticed Google maintained Kernel 4.1 AOSP didn't cherry-pick
> the patch either. Could you please help to check this issue, Thanks.
>
Well, does reverting my patch make the issue go away?
How to do you trigger it?
Thanks,
//richard
prev parent reply other threads:[~2016-03-04 19:20 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-04 2:21 UBIFS Dump Stack on Android Han Xu
2016-03-04 19:20 ` Richard Weinberger [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=56D9DFEE.7040106@nod.at \
--to=richard@nod.at \
--cc=linux-mtd@lists.infradead.org \
--cc=xhnjupt@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;
as well as URLs for NNTP newsgroup(s).