All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jeff Liu <jeff.liu@oracle.com>
To: Dave Chinner <david@fromorbit.com>
Cc: "xfs@oss.sgi.com" <xfs@oss.sgi.com>
Subject: Re: [PATCH 5/5] xfs: use xfs_ialloc_blks_per_cluster in xfs_imap
Date: Thu, 12 Dec 2013 11:16:37 +0800	[thread overview]
Message-ID: <52A92A95.5020607@oracle.com> (raw)
In-Reply-To: <20131211233938.GR10988@dastard>

On 12/12 2013 07:39 AM, Dave Chinner wrote:
> On Wed, Dec 11, 2013 at 09:48:35PM +0800, Jeff Liu wrote:
>> From: Jie Liu <jeff.liu@oracle.com>
>>
>> Use xfs_ialloc_blks_per_cluster() in xfs_imap().  Please note that we
>> previously calculate the number of blocks per cluster without taking
>> the situation of that the inode cluster size might be equal to or less
>> than the SB blocksize into account.  Maybe there is a chance to cause
>> potential issues after handling an untrusted inode number lookup and
>> proceed to check if the inode number maps to a block is outsides the
>> file system bounds or not.
> 
> I don't think there's any issues here - after all the inode lookups
> and mapping is done, the code in xfs_imap checks that the cluster
> that the inode is mapped to lies wholly within the filesystem
> boundaries. Hence I think you can remove that from the patch
> descritpion.
Ah, you're right because the current logic can handle it well if
blks_per_cluster > 1, or there is no influence to calculate the
cluster_agbno if blks_per_cluster == 1. :)

Thanks,
-Jeff

_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs

      reply	other threads:[~2013-12-12  3:16 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-12-11 13:48 [PATCH 5/5] xfs: use xfs_ialloc_blks_per_cluster in xfs_imap Jeff Liu
2013-12-11 23:39 ` Dave Chinner
2013-12-12  3:16   ` Jeff Liu [this message]

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=52A92A95.5020607@oracle.com \
    --to=jeff.liu@oracle.com \
    --cc=david@fromorbit.com \
    --cc=xfs@oss.sgi.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 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.