From: Greg KH <greg@kroah.com>
To: Badari Pulavarty <pbadari@us.ibm.com>
Cc: lkml <linux-kernel@vger.kernel.org>, stable@kernel.org, akpm@osdl.org
Subject: Re: [stable] [PATCH] ext3 -nobh option causes oops (2.6.17.7)
Date: Thu, 3 Aug 2006 00:13:08 -0700 [thread overview]
Message-ID: <20060803071308.GH26354@kroah.com> (raw)
In-Reply-To: <1154032961.29920.17.camel@dyn9047017100.beaverton.ibm.com>
On Thu, Jul 27, 2006 at 01:42:41PM -0700, Badari Pulavarty wrote:
> Hi Andrew,
>
> ext3 -nobh option causes kernel oops on files other than IFREG -
> since the modification to them are journalled anyway and the
> code expects to have buffer_head attached to it.
>
> We need this patch for stable series also.
>
> Thanks,
> Badari
>
> For files other than IFREG, nobh option doesn't make sense.
> Modifications to them are journalled and needs buffer heads
> to do that. Without this patch, we get kernel oops in page_buffers().
>
> Signed-off-by: Badari Pulavarty <pbadari@us.ibm.com>
Queued to -stable.
thanks,
greg k-h
prev parent reply other threads:[~2006-08-03 7:17 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-27 20:42 [PATCH] ext3 -nobh option causes oops (2.6.17.7) Badari Pulavarty
2006-08-03 7:13 ` Greg KH [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=20060803071308.GH26354@kroah.com \
--to=greg@kroah.com \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pbadari@us.ibm.com \
--cc=stable@kernel.org \
/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