From: Jens Axboe <jens.axboe@oracle.com>
To: "Jörn Engel" <joern@logfs.org>
Cc: linux-fsdevel@vger.kernel.org, Nick Piggin <npiggin@suse.de>,
David Woodhouse <dwmw2@infradead.org>,
linux-mtd@lists.infradead.org, linux-kernel@vger.kernel.org
Subject: Re: [patch 0/15] LogFS take five
Date: Mon, 7 Apr 2008 11:17:19 +0200 [thread overview]
Message-ID: <20080407091719.GO12774@kernel.dk> (raw)
In-Reply-To: <20080407091047.GD22431@logfs.org>
On Mon, Apr 07 2008, Jörn Engel wrote:
> On Mon, 7 April 2008 10:28:41 +0200, Jens Axboe wrote:
> > >
> > > fs/block_dev.c | 2 +-
> > > 1 file changed, 1 insertion(+), 1 deletion(-)
> > >
> > > --- linux-2.6.24logfs/fs/block_dev.c~blockdev_nofs 2008-04-07 10:19:08.627413077 +0200
> > > +++ linux-2.6.24logfs/fs/block_dev.c 2008-04-07 10:20:56.927117162 +0200
> > > @@ -586,7 +586,7 @@ struct block_device *bdget(dev_t dev)
> > > inode->i_rdev = dev;
> > > inode->i_bdev = bdev;
> > > inode->i_data.a_ops = &def_blk_aops;
> > > - mapping_set_gfp_mask(&inode->i_data, GFP_USER);
> > > + mapping_set_gfp_mask(&inode->i_data, GFP_USER & ~__GFP_FS);
> > > inode->i_data.backing_dev_info = &default_backing_dev_info;
> > > spin_lock(&bdev_lock);
> > > list_add(&bdev->bd_list, &all_bdevs);
> >
> > It's not the right fix, generally GFP_FS is fine here. So do that in
> > logfs when you cannot traverse back into the fs, eg
> >
> > mapping_gfp_mask(mapping) & ~__GFP_FS;
> >
> > locally.
>
> struct address_space *mapping;
>
> /* Prevent bdev from calling back into fs */
> mapping = &logfs_super(sb)->s_bdev->bd_inode->i_data;
> mapping_set_gfp_mask(mapping, mapping_gfp_mask(mapping) & ~__GFP_FS);
>
> bd_inode has an interesting comment:
> struct inode * bd_inode; /* will die */
>
> Should I be worried about that? It seems to predate git history, so
> I'm not too concerned about immediate changes.
I'd just ignore it, it's widely used anyway...
--
Jens Axboe
WARNING: multiple messages have this Message-ID (diff)
From: Jens Axboe <jens.axboe@oracle.com>
To: "Jörn Engel" <joern@logfs.org>
Cc: linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org,
linux-mtd@lists.infradead.org, Nick Piggin <npiggin@suse.de>,
David Woodhouse <dwmw2@infradead.org>
Subject: Re: [patch 0/15] LogFS take five
Date: Mon, 7 Apr 2008 11:17:19 +0200 [thread overview]
Message-ID: <20080407091719.GO12774@kernel.dk> (raw)
In-Reply-To: <20080407091047.GD22431@logfs.org>
On Mon, Apr 07 2008, Jörn Engel wrote:
> On Mon, 7 April 2008 10:28:41 +0200, Jens Axboe wrote:
> > >
> > > fs/block_dev.c | 2 +-
> > > 1 file changed, 1 insertion(+), 1 deletion(-)
> > >
> > > --- linux-2.6.24logfs/fs/block_dev.c~blockdev_nofs 2008-04-07 10:19:08.627413077 +0200
> > > +++ linux-2.6.24logfs/fs/block_dev.c 2008-04-07 10:20:56.927117162 +0200
> > > @@ -586,7 +586,7 @@ struct block_device *bdget(dev_t dev)
> > > inode->i_rdev = dev;
> > > inode->i_bdev = bdev;
> > > inode->i_data.a_ops = &def_blk_aops;
> > > - mapping_set_gfp_mask(&inode->i_data, GFP_USER);
> > > + mapping_set_gfp_mask(&inode->i_data, GFP_USER & ~__GFP_FS);
> > > inode->i_data.backing_dev_info = &default_backing_dev_info;
> > > spin_lock(&bdev_lock);
> > > list_add(&bdev->bd_list, &all_bdevs);
> >
> > It's not the right fix, generally GFP_FS is fine here. So do that in
> > logfs when you cannot traverse back into the fs, eg
> >
> > mapping_gfp_mask(mapping) & ~__GFP_FS;
> >
> > locally.
>
> struct address_space *mapping;
>
> /* Prevent bdev from calling back into fs */
> mapping = &logfs_super(sb)->s_bdev->bd_inode->i_data;
> mapping_set_gfp_mask(mapping, mapping_gfp_mask(mapping) & ~__GFP_FS);
>
> bd_inode has an interesting comment:
> struct inode * bd_inode; /* will die */
>
> Should I be worried about that? It seems to predate git history, so
> I'm not too concerned about immediate changes.
I'd just ignore it, it's widely used anyway...
--
Jens Axboe
WARNING: multiple messages have this Message-ID (diff)
From: Jens Axboe <jens.axboe@oracle.com>
To: "Jörn Engel" <joern@logfs.org>
Cc: linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org,
linux-mtd@lists.infradead.org, Nick Piggin <npiggin@suse.de>,
David Woodhouse <dwmw2@infradead.org>
Subject: Re: [patch 0/15] LogFS take five
Date: Mon, 7 Apr 2008 11:17:19 +0200 [thread overview]
Message-ID: <20080407091719.GO12774@kernel.dk> (raw)
In-Reply-To: <20080407091047.GD22431@logfs.org>
On Mon, Apr 07 2008, Jörn Engel wrote:
> On Mon, 7 April 2008 10:28:41 +0200, Jens Axboe wrote:
> > >
> > > fs/block_dev.c | 2 +-
> > > 1 file changed, 1 insertion(+), 1 deletion(-)
> > >
> > > --- linux-2.6.24logfs/fs/block_dev.c~blockdev_nofs 2008-04-07 10:19:08.627413077 +0200
> > > +++ linux-2.6.24logfs/fs/block_dev.c 2008-04-07 10:20:56.927117162 +0200
> > > @@ -586,7 +586,7 @@ struct block_device *bdget(dev_t dev)
> > > inode->i_rdev = dev;
> > > inode->i_bdev = bdev;
> > > inode->i_data.a_ops = &def_blk_aops;
> > > - mapping_set_gfp_mask(&inode->i_data, GFP_USER);
> > > + mapping_set_gfp_mask(&inode->i_data, GFP_USER & ~__GFP_FS);
> > > inode->i_data.backing_dev_info = &default_backing_dev_info;
> > > spin_lock(&bdev_lock);
> > > list_add(&bdev->bd_list, &all_bdevs);
> >
> > It's not the right fix, generally GFP_FS is fine here. So do that in
> > logfs when you cannot traverse back into the fs, eg
> >
> > mapping_gfp_mask(mapping) & ~__GFP_FS;
> >
> > locally.
>
> struct address_space *mapping;
>
> /* Prevent bdev from calling back into fs */
> mapping = &logfs_super(sb)->s_bdev->bd_inode->i_data;
> mapping_set_gfp_mask(mapping, mapping_gfp_mask(mapping) & ~__GFP_FS);
>
> bd_inode has an interesting comment:
> struct inode * bd_inode; /* will die */
>
> Should I be worried about that? It seems to predate git history, so
> I'm not too concerned about immediate changes.
I'd just ignore it, it's widely used anyway...
--
Jens Axboe
--
To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2008-04-07 9:17 UTC|newest]
Thread overview: 85+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-01 18:13 [patch 0/15] LogFS take five joern
2008-04-01 18:13 ` joern
2008-04-01 18:13 ` [patch 7/15] fs/logfs/gc.c joern
2008-04-01 18:13 ` [patch 10/15] fs/logfs/memtree.c joern
2008-04-10 14:07 ` Arnd Bergmann
2008-04-10 14:07 ` Arnd Bergmann
2008-04-10 14:07 ` Arnd Bergmann
2008-04-11 10:37 ` Jörn Engel
2008-04-11 10:37 ` Jörn Engel
2008-04-11 10:37 ` Jörn Engel
2008-04-01 18:13 ` [patch 13/15] fs/logfs/super.c joern
2008-04-01 18:13 ` [patch 1/15] Makefiles and Kconfig joern
2008-04-07 8:28 ` Christian Borntraeger
2008-04-07 8:28 ` Christian Borntraeger
2008-04-07 8:40 ` Jörn Engel
2008-04-07 8:40 ` Jörn Engel
2008-04-07 8:40 ` Jörn Engel
2008-04-08 0:30 ` Arnd Bergmann
2008-04-08 0:30 ` Arnd Bergmann
2008-04-08 8:33 ` Jörn Engel
2008-04-08 8:33 ` Jörn Engel
2008-04-08 8:33 ` Jörn Engel
2008-04-08 13:41 ` Arnd Bergmann
2008-04-08 13:41 ` Arnd Bergmann
2008-04-08 13:41 ` Arnd Bergmann
2008-04-08 13:52 ` Jörn Engel
2008-04-08 13:52 ` Jörn Engel
2008-04-08 13:52 ` Jörn Engel
2008-04-01 18:13 ` [patch 4/15] fs/logfs/compr.c joern
2008-04-10 14:13 ` Arnd Bergmann
2008-04-10 14:13 ` Arnd Bergmann
2008-04-10 14:13 ` Arnd Bergmann
2008-04-11 10:41 ` Jörn Engel
2008-04-11 10:41 ` Jörn Engel
2008-04-01 18:13 ` [patch 2/15] fs/logfs/logfs_abi.h joern
2008-04-08 0:24 ` Arnd Bergmann
2008-04-08 0:24 ` Arnd Bergmann
2008-04-08 0:24 ` Arnd Bergmann
2008-04-08 9:39 ` Jörn Engel
2008-04-08 9:39 ` Jörn Engel
2008-04-08 9:39 ` Jörn Engel
2008-04-08 21:52 ` Andres Salomon
2008-04-08 21:52 ` Andres Salomon
2008-04-09 12:08 ` Jörn Engel
2008-04-09 12:08 ` Jörn Engel
2008-04-09 12:08 ` Jörn Engel
2008-04-01 18:13 ` [patch 12/15] fs/logfs/segment.c joern
2008-04-01 18:13 ` [patch 15/15] fs/logfs/dev_mtd.c joern
2008-04-01 18:13 ` [patch 8/15] fs/logfs/inode.c joern
2008-04-04 6:57 ` Kyungmin Park
2008-04-04 6:57 ` Kyungmin Park
2008-04-07 11:12 ` Jörn Engel
2008-04-07 11:12 ` Jörn Engel
2008-04-07 11:12 ` Jörn Engel
2008-04-01 18:13 ` [patch 3/15] fs/logfs/logfs.h joern
2008-04-08 0:35 ` Arnd Bergmann
2008-04-08 0:35 ` Arnd Bergmann
2008-04-08 0:35 ` Arnd Bergmann
2008-04-08 9:41 ` Jörn Engel
2008-04-08 9:41 ` Jörn Engel
2008-04-08 9:41 ` Jörn Engel
2008-04-01 18:13 ` [patch 6/15] fs/logfs/file.c joern
2008-04-01 18:13 ` [patch 11/15] fs/logfs/readwrite.c joern
2008-04-01 18:13 ` [patch 5/15] fs/logfs/dir.c joern
2008-04-04 6:22 ` Kyungmin Park
2008-04-04 6:22 ` Kyungmin Park
2008-04-01 18:13 ` [patch 14/15] fs/logfs/dev_bdev.c joern
2008-04-01 18:13 ` [patch 9/15] fs/logfs/journal.c joern
2008-04-03 17:13 ` [patch 0/15] LogFS take five^Wsix Jörn Engel
2008-04-03 17:13 ` Jörn Engel
2008-04-03 17:13 ` Jörn Engel
2008-04-04 11:46 ` [patch 0/15] LogFS take five Jens Axboe
2008-04-04 11:46 ` Jens Axboe
2008-04-07 8:22 ` Jörn Engel
2008-04-07 8:22 ` Jörn Engel
2008-04-07 8:22 ` Jörn Engel
2008-04-07 8:28 ` Jens Axboe
2008-04-07 8:28 ` Jens Axboe
2008-04-07 8:28 ` Jens Axboe
2008-04-07 9:10 ` Jörn Engel
2008-04-07 9:10 ` Jörn Engel
2008-04-07 9:10 ` Jörn Engel
2008-04-07 9:17 ` Jens Axboe [this message]
2008-04-07 9:17 ` Jens Axboe
2008-04-07 9:17 ` Jens Axboe
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=20080407091719.GO12774@kernel.dk \
--to=jens.axboe@oracle.com \
--cc=dwmw2@infradead.org \
--cc=joern@logfs.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=npiggin@suse.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.