From: Ryusuke Konishi <konishi.ryusuke@lab.ntt.co.jp>
To: jaxboe@fusionio.com
Cc: konishi.ryusuke@lab.ntt.co.jp, linux-nilfs@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] nilfs2: fix oops due to a bad aops initialization
Date: Wed, 30 Mar 2011 20:22:15 +0900 (JST) [thread overview]
Message-ID: <20110330.202215.163256481.ryusuke@osrg.net> (raw)
In-Reply-To: <4D930F02.4070409@fusionio.com>
On Wed, 30 Mar 2011 13:07:46 +0200, Jens Axboe <jaxboe@fusionio.com> wrote:
> On 2011-03-30 06:25, Ryusuke Konishi wrote:
> > diff --git a/fs/nilfs2/page.c b/fs/nilfs2/page.c
> > index 4d2a1ee..9d2dc6b 100644
> > --- a/fs/nilfs2/page.c
> > +++ b/fs/nilfs2/page.c
> > @@ -495,12 +495,14 @@ unsigned nilfs_page_count_clean_buffers(struct page *page,
> > void nilfs_mapping_init(struct address_space *mapping,
> > struct backing_dev_info *bdi)
> > {
> > + static const struct address_space_operations empty_aops;
> > +
> > mapping->host = NULL;
> > mapping->flags = 0;
> > mapping_set_gfp_mask(mapping, GFP_NOFS);
> > mapping->assoc_mapping = NULL;
> > mapping->backing_dev_info = bdi;
> > - mapping->a_ops = NULL;
> > + mapping->a_ops = &empty_aops;
> > }
>
> Hmm wait, inode init should set the mapping aops to an empty type
> already. Does the OOPS go away if you just remove the mapping->a_ops =
> NULL assignment?
>
> --
> Jens Axboe
Nilfs has two mappings in each inode, one for data pages and another
for btree nodes. The aops initialization is neede for the latter one.
Ryusuke Konishi
prev parent reply other threads:[~2011-03-30 11:22 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-30 4:25 Ryusuke Konishi
2011-03-30 7:47 ` Jens Axboe
2011-03-30 11:07 ` Jens Axboe
2011-03-30 11:17 ` Jens Axboe
2011-03-30 11:48 ` Ryusuke Konishi
2011-03-30 11:51 ` Jens Axboe
2011-03-30 11:22 ` Ryusuke Konishi [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=20110330.202215.163256481.ryusuke@osrg.net \
--to=konishi.ryusuke@lab.ntt.co.jp \
--cc=jaxboe@fusionio.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nilfs@vger.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
all inboxes | Powered by JetHome®