From: Dave Kleikamp <dave.kleikamp@oracle.com>
To: Lukas Czerner <lczerner@redhat.com>
Cc: jfs-discussion@lists.sourceforge.net, linux-fsdevel@vger.kernel.org
Subject: Re: [PATCH] jfs: Fix FITRIM argument handling
Date: Wed, 17 Oct 2012 09:33:35 -0500 [thread overview]
Message-ID: <507EC1BF.10004@oracle.com> (raw)
In-Reply-To: <1350380286-16929-1-git-send-email-lczerner@redhat.com>
On 10/16/2012 04:38 AM, Lukas Czerner wrote:
> Currently when 'range->start' is beyond the end of file system
> nothing is done and that fact is ignored, where in fact we should return
> EINVAL. The same problem is when 'range.len' is smaller than file system
> block.
>
> Fix this by adding check for such conditions and return EINVAL
> appropriately.
>
> Signed-off-by: Lukas Czerner <lczerner@redhat.com>
Looks good. Pushed out to
git://github.com/kleikamp/linux-shaggy.git jfs-next
Should make the next linux-next build.
Thanks,
Shaggy
> ---
> fs/jfs/jfs_discard.c | 16 ++++++++++------
> 1 files changed, 10 insertions(+), 6 deletions(-)
>
> diff --git a/fs/jfs/jfs_discard.c b/fs/jfs/jfs_discard.c
> index 9947563..dfcd503 100644
> --- a/fs/jfs/jfs_discard.c
> +++ b/fs/jfs/jfs_discard.c
> @@ -83,7 +83,7 @@ int jfs_ioc_trim(struct inode *ip, struct fstrim_range *range)
> struct bmap *bmp = JFS_SBI(ip->i_sb)->bmap;
> struct super_block *sb = ipbmap->i_sb;
> int agno, agno_end;
> - s64 start, end, minlen;
> + u64 start, end, minlen;
> u64 trimmed = 0;
>
> /**
> @@ -93,15 +93,19 @@ int jfs_ioc_trim(struct inode *ip, struct fstrim_range *range)
> * minlen: minimum extent length in Bytes
> */
> start = range->start >> sb->s_blocksize_bits;
> - if (start < 0)
> - start = 0;
> end = start + (range->len >> sb->s_blocksize_bits) - 1;
> - if (end >= bmp->db_mapsize)
> - end = bmp->db_mapsize - 1;
> minlen = range->minlen >> sb->s_blocksize_bits;
> - if (minlen <= 0)
> + if (minlen == 0)
> minlen = 1;
>
> + if (minlen > bmp->db_agsize ||
> + start >= bmp->db_mapsize ||
> + range->len < sb->s_blocksize)
> + return -EINVAL;
> +
> + if (end >= bmp->db_mapsize)
> + end = bmp->db_mapsize - 1;
> +
> /**
> * we trim all ag's within the range
> */
>
prev parent reply other threads:[~2012-10-17 14:33 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-16 9:38 [PATCH] jfs: Fix FITRIM argument handling Lukas Czerner
2012-10-16 18:57 ` [Jfs-discussion] " Tino Reichardt
2012-10-17 14:33 ` Dave Kleikamp [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=507EC1BF.10004@oracle.com \
--to=dave.kleikamp@oracle.com \
--cc=jfs-discussion@lists.sourceforge.net \
--cc=lczerner@redhat.com \
--cc=linux-fsdevel@vger.kernel.org \
/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.