From: Linus Torvalds <torvalds@linux-foundation.org>
To: Josef Bacik <josef@redhat.com>
Cc: akpm@linux-foundation.org, linux-fsdevel@vger.kernel.org,
linux-kernel@vger.kernel.org, randy.dunlap@oracle.com
Subject: Re: [PATCH] cleanup block based fiemap
Date: Fri, 23 Apr 2010 08:27:02 -0700 (PDT) [thread overview]
Message-ID: <alpine.LFD.2.00.1004230825481.3739@i5.linux-foundation.org> (raw)
In-Reply-To: <20100423151857.GD2351@localhost.localdomain>
On Fri, 23 Apr 2010, Josef Bacik wrote:
>
> __generic_block_fiemap is called by generic_block_fiemap which takes the
> i_mutex. The only reason we have __generic_block_fiemap is because gfs2 needs
> to do its own locking magic before we go calling get_block. The idea is that
> the file size doesn't change while we're doing this.
Ok, maybe just a comment then..
> As for reading the size several times, I can read it once and store it in a
> local variable if you prefer, but theres no way to know if len is smaller than
> the size or not, which is why I'm constantly doing i_size_read(). If thats what
> you would prefer I can do that, just let me know.
.. or a comment _and_ a "read size once into a variable". Not a big deal,
it just wasn't entirely clear to me and I hadn't checked the callchain.
> > Issue #2: "blk_to_logical(inode, 0)"? WTF? Since when has shifting zero
> > ever resulted in anything interesting or relevant? There's at least two of
> > those things.
> >
>
> Umm, yeah I'm sorry? I have no idea why I did that. I think its because I was
> getting the logical offset of the first block + size, which is just stupid
> because the logical offset is 0, so all I can say is I'm sorry that me a year
> ago was alot dumber than me now :). Thanks,
Ok, fix that, and I think the patch will be a clear improvement.
Linus
next prev parent reply other threads:[~2010-04-23 15:28 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-23 14:44 Josef Bacik
2010-04-23 15:00 ` Linus Torvalds
2010-04-23 15:18 ` Josef Bacik
2010-04-23 15:27 ` Linus Torvalds [this message]
2010-04-23 15:47 ` Josef Bacik
2010-04-23 15:56 ` Linus Torvalds
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=alpine.LFD.2.00.1004230825481.3739@i5.linux-foundation.org \
--to=torvalds@linux-foundation.org \
--cc=akpm@linux-foundation.org \
--cc=josef@redhat.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=randy.dunlap@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
all inboxes | Powered by JetHome®