From: Richard Weinberger <richard@nod.at>
To: ocfs2-devel@oss.oracle.com
Cc: ocfs2-user@oss.oracle.com, linux-kernel@vger.kernel.org,
viro@zeniv.linux.org.uk, mfasheh@suse.com, jlbec@evilplan.org,
linux-fsdevel@vger.kernel.org, david@sigma-star.at
Subject: OCFS2 mainline state?
Date: Mon, 25 Feb 2013 21:33:34 +0100 [thread overview]
Message-ID: <512BCA9E.4090702@nod.at> (raw)
Hi!
Today I encountered the following problem on v3.8:
[ 28.940032] general protection fault: 0000 [#1] PREEMPT SMP
...
[ 28.984953] Call Trace:
[ 28.986628 [<ffffffffa04cb200>] ocfs2_fast_symlink_readpage+0x70/0x1b0 [ocfs2]
[ 28.988302] [<ffffffff8110dc49>] ? add_to_page_cache_lru+0x29/0x40
[ 28.989942] [<ffffffff8110ddca>] do_read_cache_page+0x7a/0x170
[ 28.991573] [<ffffffff8110def4>] read_cache_page_async+0x14/0x20
[ 28.993212] [<ffffffff8110df09>] read_cache_page+0x9/0x20
[ 28.994827] [<ffffffff81170ae5>] page_getlink.isra.9+0x25/0x80
[ 28.996442] [<ffffffff81170b61>] page_follow_link_light+0x21/0x40
[ 28.998049] [<ffffffff8117090d>] generic_readlink+0x3d/0xa0
[ 28.999653] [<ffffffff8116c0db>] sys_readlinkat+0xfb/0x130
[ 29.001246] [<ffffffff8116c126>] sys_readlink+0x16/0x20
[ 29.002839] [<ffffffff815d8dad>] system_call_fastpath+0x1a/0x1f
To my utter astonishment I found out that the issue is known since August 2012.
And there is also a trivial fix for it.[0]
The said fix found it's way into Oracle Unbreakable Linux very quickly,
but not into mainline.[1]
Now I'm wondering how much Oracle really cares about OCFS2 in mainline?
Maybe there are some more unfixed vulnerabilities?
Not amused,
//richard
[0] http://www.mail-archive.com/ocfs2-devel@oss.oracle.com/msg07774.html
[1] https://oss.oracle.com/pipermail/el-errata/2012-October/003103.html
next reply other threads:[~2013-02-25 20:33 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-25 20:33 Richard Weinberger [this message]
2013-02-25 21:11 ` OCFS2 mainline state? Mark Fasheh
2013-02-25 21:16 ` Al Viro
2013-02-25 21:28 ` Mark Fasheh
2013-03-02 10:05 ` Joel Becker
2013-02-25 21:30 ` Mark Fasheh
2013-02-25 21:37 ` Smart Weblications GmbH - Florian Wiessner
2013-03-02 10:15 ` Vincent ETIENNE
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=512BCA9E.4090702@nod.at \
--to=richard@nod.at \
--cc=david@sigma-star.at \
--cc=jlbec@evilplan.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mfasheh@suse.com \
--cc=ocfs2-devel@oss.oracle.com \
--cc=ocfs2-user@oss.oracle.com \
--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).