From: Chao Yu <chao@kernel.org>
To: Georg Veichtlbauer <georg@veichtlbauer.net>,
Jaegeuk Kim <jaegeuk@kernel.org>,
Hou Pengyang <houpengyang@huawei.com>,
Yunlong Song <yunlong.song@huawei.com>,
bintian.wang@huawei.com
Cc: linux-f2fs-devel@lists.sourceforge.net
Subject: Re: Kernel OOPS in f2fs-stable on ARM
Date: Sat, 21 May 2016 00:20:30 +0800 [thread overview]
Message-ID: <4bc7dc8c-9e08-b36a-01d0-f2e50d42a4e8@kernel.org> (raw)
In-Reply-To: <47ad19eec862bf788de5636e58d897b0@mail.tophosting.at>
Hi all,
I found a bug related to panic issue in ->evict_inode, I sent a patch for
fixing, I hope the patch can fix your problem, could you review or test it?
Thanks,
On 2016/5/19 0:58, Georg Veichtlbauer wrote:
> Hi,
> sorry for the late reply. Unfortunately, that patch did not fix the issue. Many
> other devices are having this problem, so my fellow CM maintainers start
> reverting to an old stable release. I'd prefer fixing the issue though.... ideas?
> Cheers,
> georg
------------------------------------------------------------------------------
Mobile security can be enabling, not merely restricting. Employees who
bring their own devices (BYOD) to work are irked by the imposition of MDM
restrictions. Mobile Device Manager Plus allows you to control only the
apps on BYO-devices by containerizing them, leaving personal data untouched!
https://ad.doubleclick.net/ddm/clk/304595813;131938128;j
prev parent reply other threads:[~2016-05-20 16:20 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-22 6:58 Kernel OOPS in f2fs-stable on ARM Georg Veichtlbauer
2016-04-24 13:51 ` Chao Yu
[not found] ` <47ad19eec862bf788de5636e58d897b0@mail.tophosting.at>
2016-05-20 16:20 ` Chao Yu [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=4bc7dc8c-9e08-b36a-01d0-f2e50d42a4e8@kernel.org \
--to=chao@kernel.org \
--cc=bintian.wang@huawei.com \
--cc=georg@veichtlbauer.net \
--cc=houpengyang@huawei.com \
--cc=jaegeuk@kernel.org \
--cc=linux-f2fs-devel@lists.sourceforge.net \
--cc=yunlong.song@huawei.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).