From: Christoph Hellwig <hch@infradead.org>
To: Chris Mason <mason@suse.com>
Cc: Christoph Hellwig <hch@infradead.org>, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] lockfs patch for 2.6
Date: Fri, 12 Mar 2004 15:51:45 +0000 [thread overview]
Message-ID: <20040312155145.A16751@infradead.org> (raw)
In-Reply-To: <1079106653.4185.171.camel@watt.suse.com>; from mason@suse.com on Fri, Mar 12, 2004 at 10:50:53AM -0500
On Fri, Mar 12, 2004 at 10:50:53AM -0500, Chris Mason wrote:
> Would you like this better:
>
> device mapper code:
> fsync_bdev(bdev);
> s = freeze_fs(bdev);
> < create snap shot >
> thaw_fs(bdev, s);
Hmm, I actually thought about moving the fsync_bdev into
freeze_fs, but having it separate might more sense indeed.
> thaw_fs needs the bdev so it can up the bdev mount semaphore.
sb->s_bdev should do it aswell
next prev parent reply other threads:[~2004-03-12 15:52 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-09 21:31 [PATCH] lockfs patch for 2.6 Chris Mason
2004-03-12 9:31 ` Christoph Hellwig
2004-03-12 15:50 ` Chris Mason
2004-03-12 15:51 ` Christoph Hellwig [this message]
2004-03-13 13:14 ` Christoph Hellwig
2004-03-13 15:20 ` Chris Mason
2004-03-13 16:33 ` Christoph Hellwig
2004-03-14 14:00 ` Christoph Hellwig
2004-03-14 15:23 ` Chris Mason
2004-03-26 10:25 ` Christoph Hellwig
2004-03-26 13:28 ` Chris Mason
2004-04-01 20:35 ` Chris Mason
2004-04-01 22:32 ` Kevin Corry
2004-04-02 20:00 ` Kevin Corry
2004-04-02 20:02 ` Christoph Hellwig
2004-04-02 20:26 ` Kevin Corry
2004-03-14 18:44 ` Andrew Morton
2004-03-14 18:52 ` Christoph Hellwig
2004-03-14 18:56 ` Chris Mason
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=20040312155145.A16751@infradead.org \
--to=hch@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mason@suse.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