From: Adrian Bunk <bunk@stusta.de>
To: Badari Pulavarty <pbadari@us.ibm.com>, linux-ext4@vger.kernel.org
Subject: Re: [patch 15/23] ext3 -nobh option causes oops
Date: Thu, 16 Nov 2006 23:51:54 +0100 [thread overview]
Message-ID: <20061116225154.GK31879@stusta.de> (raw)
In-Reply-To: <20060804054003.GP769@kroah.com>
It seems this patch that went into 2.6.17.8 should also be included in
the 2.6.16.x branch, or do I miss anything?
TIA
Adrian
On Thu, Aug 03, 2006 at 10:40:03PM -0700, Greg KH wrote:
> -stable review patch. If anyone has any objections, please let us know.
>
> ------------------
> From: Badari Pulavarty <pbadari@us.ibm.com>
>
> 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>
> Signed-off-by: Andrew Morton <akpm@osdl.org>
> Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
>
> ---
> fs/ext3/inode.c | 6 +++---
> 1 file changed, 3 insertions(+), 3 deletions(-)
>
> --- linux-2.6.17.7.orig/fs/ext3/inode.c
> +++ linux-2.6.17.7/fs/ext3/inode.c
> @@ -1159,7 +1159,7 @@ retry:
> ret = PTR_ERR(handle);
> goto out;
> }
> - if (test_opt(inode->i_sb, NOBH))
> + if (test_opt(inode->i_sb, NOBH) && ext3_should_writeback_data(inode))
> ret = nobh_prepare_write(page, from, to, ext3_get_block);
> else
> ret = block_prepare_write(page, from, to, ext3_get_block);
> @@ -1245,7 +1245,7 @@ static int ext3_writeback_commit_write(s
> if (new_i_size > EXT3_I(inode)->i_disksize)
> EXT3_I(inode)->i_disksize = new_i_size;
>
> - if (test_opt(inode->i_sb, NOBH))
> + if (test_opt(inode->i_sb, NOBH) && ext3_should_writeback_data(inode))
> ret = nobh_commit_write(file, page, from, to);
> else
> ret = generic_commit_write(file, page, from, to);
> @@ -1495,7 +1495,7 @@ static int ext3_writeback_writepage(stru
> goto out_fail;
> }
>
> - if (test_opt(inode->i_sb, NOBH))
> + if (test_opt(inode->i_sb, NOBH) && ext3_should_writeback_data(inode))
> ret = nobh_writepage(page, ext3_get_block, wbc);
> else
> ret = block_write_full_page(page, ext3_get_block, wbc);
>
next parent reply other threads:[~2006-11-16 22:51 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20060804053258.391158155@quad.kroah.org>
[not found] ` <20060804054003.GP769@kroah.com>
2006-11-16 22:51 ` Adrian Bunk [this message]
2006-11-16 23:07 ` [patch 15/23] ext3 -nobh option causes oops Badari Pulavarty
2006-11-17 16:47 ` Adrian Bunk
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=20061116225154.GK31879@stusta.de \
--to=bunk@stusta.de \
--cc=linux-ext4@vger.kernel.org \
--cc=pbadari@us.ibm.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