From: Joel Becker <Joel.Becker@oracle.com>
To: "Patrick J. LoPresti" <lopresti@gmail.com>
Cc: Andreas Dilger <adilger@dilger.ca>,
linux-fsdevel@vger.kernel.org, linux-ext4@vger.kernel.org,
linux-kernel@vger.kernel.org, ocfs2-devel@oss.oracle.com
Subject: Re: [Ocfs2-devel] [PATCH 2/2] OCFS2: Allow huge (> 16 TiB) volumes to mount
Date: Tue, 13 Jul 2010 01:10:13 -0700 [thread overview]
Message-ID: <20100713081013.GA31479@mail.oracle.com> (raw)
In-Reply-To: <AANLkTinsQjWD1t1lO_BHnM-afzYyl7TKKdIcNZEVMg6n@mail.gmail.com>
On Mon, Jul 12, 2010 at 10:00:10PM -0700, Patrick J. LoPresti wrote:
> On Mon, Jul 12, 2010 at 9:46 PM, Andreas Dilger <adilger@dilger.ca> wrote:
> > On 2010-07-12, at 19:08, Patrick J. LoPresti wrote:
> >>
> >> Are you suggesting I need to do this before my patch is accepted at
> >> all? Or is this a refactoring that can happen later?
> >
> > I'm just suggesting it should be done at some point. I thought it would be better to do it first, rather than add yet another copy of this code. That said, I hate to block useful fixes because of cleanup (and I have no control over OCFS2 anyway :-). However, I've found that once the fix is in people usually forget (or become too busy) to do the cleanup and it just lingers on unseen.
>
> I hear you.
>
> I do not object to factoring out the basic addressability test and
> using it in my patch, leaving it for others -- like yourself :-) -- to
> modify other file systems to invoke it.
I think you should modify ext3 and xfs, as they clearly are
partaking of this functionality. I'll happily review it for you. Put
the call in fs/libfs.c. Call it generic_check_addressable(struct
super_block *super).
Joel
--
"The only way to get rid of a temptation is to yield to it."
- Oscar Wilde
Joel Becker
Consulting Software Developer
Oracle
E-mail: joel.becker@oracle.com
Phone: (650) 506-8127
--
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:[~2010-07-13 8:11 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-11 17:03 [PATCH 1/2] JBD2: Allow feature checks before journal recovery Patrick J. LoPresti
2010-07-11 17:04 ` [PATCH 2/2] OCFS2: Allow huge (> 16 TiB) volumes to mount Patrick J. LoPresti
2010-07-13 0:21 ` Andreas Dilger
2010-07-13 1:08 ` Patrick J. LoPresti
2010-07-13 1:25 ` Dave Chinner
2010-07-13 1:37 ` Patrick J. LoPresti
2010-07-13 4:46 ` Andreas Dilger
2010-07-13 5:00 ` Patrick J. LoPresti
2010-07-13 8:10 ` Joel Becker [this message]
2010-07-21 17:27 ` [PATCH 1/2] JBD2: Allow feature checks before journal recovery Jan Kara
2010-07-21 17:42 ` Patrick J. LoPresti
2010-07-21 17:50 ` Jan Kara
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=20100713081013.GA31479@mail.oracle.com \
--to=joel.becker@oracle.com \
--cc=adilger@dilger.ca \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lopresti@gmail.com \
--cc=ocfs2-devel@oss.oracle.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).