From: Christoph Hellwig <hch@infradead.org>
To: Jan Kara <jack@suse.cz>
Cc: Christoph Hellwig <hch@infradead.org>,
Alessio Igor Bogani <abogani@texware.it>,
Arnd Bergmann <arnd@arndb.de>, Tim Bird <tim.bird@am.sony.com>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 1/4] udf: Add missed protection for s_lvid_dirty
Date: Sun, 7 Nov 2010 09:27:19 -0500 [thread overview]
Message-ID: <20101107142719.GA25234@infradead.org> (raw)
In-Reply-To: <20101107141403.GF5126@quack.suse.cz>
On Sun, Nov 07, 2010 at 03:14:03PM +0100, Jan Kara wrote:
> Looking at it now, cleaner fix might be to move the counters to sbi and
> write them to the LVID only during umount. So that might be a nice cleanup
> as well.
Yes, that's what we're doing in most filesystems for these counters.
next prev parent reply other threads:[~2010-11-07 14:27 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-06 17:47 [PATCH 1/4] udf: Add missed protection for s_lvid_dirty Alessio Igor Bogani
2010-11-06 17:47 ` [PATCH 2/4] udf: Remove unnecessary bkl usages Alessio Igor Bogani
2010-11-06 18:06 ` Christoph Hellwig
2010-11-06 17:47 ` [PATCH 3/4] udf: Replace bkl with a mutex for protect udf_inode_info struct Alessio Igor Bogani
2010-11-06 18:10 ` Christoph Hellwig
2010-11-06 17:47 ` [PATCH 4/4] udf: Replace bkl with a mutex for protect udf_sb_info struct Alessio Igor Bogani
2010-11-06 18:16 ` Christoph Hellwig
2010-11-06 18:05 ` [PATCH 1/4] udf: Add missed protection for s_lvid_dirty Christoph Hellwig
2010-11-07 14:14 ` Jan Kara
2010-11-07 14:27 ` Christoph Hellwig [this message]
2010-11-07 15:06 ` Jan Kara
2010-11-15 22:46 ` Arnd Bergmann
2010-11-16 0:43 ` Jan Kara
2010-11-16 13:03 ` Alessio Igor Bogani
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=20101107142719.GA25234@infradead.org \
--to=hch@infradead.org \
--cc=abogani@texware.it \
--cc=arnd@arndb.de \
--cc=jack@suse.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=tim.bird@am.sony.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;
as well as URLs for NNTP newsgroup(s).