From: Andrew Morton <akpm@linux-foundation.org>
To: Bret Towe <magnade@gmail.com>
Cc: linux-kernel@vger.kernel.org, Joel Becker <jlbec@evilplan.org>,
Mark Fasheh <mfasheh@suse.com>,
ocfs2-devel@oss.oracle.com
Subject: Re: crash in ocfs2_fast_symlink_readpage in kernel 3.5.0
Date: Thu, 24 Jan 2013 14:30:07 -0800 [thread overview]
Message-ID: <20130124143007.39c8545f.akpm@linux-foundation.org> (raw)
In-Reply-To: <CALjC5hbMq+bc-X8Ad+=gEZLuWy3ZXm4Z0Y2w44k5UZjL4g7vqg@mail.gmail.com>
On Sat, 19 Jan 2013 20:15:33 -0800
Bret Towe <magnade@gmail.com> wrote:
> >
> > it looks like you have a patch for this problem in a queue somewhere
> > (email found on ocfs2-dev:
> > https://oss.oracle.com/pipermail/ocfs2-devel/2012-August/008677.html )
> > but its not in 3.6, any reason for the delay?
> > I've been running that patch on 3.5 for a while now likely since
> > around the time i found that email
> > and its been working well
>
> doesn't look to be in 3.7 or 3.8-git
> and from what i see on ocfs2-dev there are at least 16 other patches
> that are also being ignored?
> I'm sure if I'm bothering at this point to maintain my own patchset to
> keep ocfs2 from crashing
> that there is other folks doing the same
Please resend all OCFS2 patches, cc'ing myself, Mark, Joel and
ocfs2-devel@oss.oracle.com.
I shall then review them, merge them into -mm (and hence linux-next) so
they can get a bit of visibility and testing while the maintainers are
checking them over.
Thanks.
next prev parent reply other threads:[~2013-01-24 22:30 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-22 20:16 Bret Towe
2012-07-30 8:28 ` Joel Becker
2012-07-30 16:05 ` Bret Towe
2012-10-03 3:41 ` Bret Towe
2013-01-20 4:15 ` Bret Towe
2013-01-24 22:30 ` Andrew Morton [this message]
2013-01-25 3:40 ` Bret Towe
2013-01-29 0:46 ` Andrew Morton
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=20130124143007.39c8545f.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=jlbec@evilplan.org \
--cc=linux-kernel@vger.kernel.org \
--cc=magnade@gmail.com \
--cc=mfasheh@suse.com \
--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
all inboxes | Powered by JetHome®