linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Josef Bacik <jbacik@fusionio.com>
To: Wang Shilong <wangsl.fnst@cn.fujitsu.com>
Cc: Josef Bacik <jbacik@fusionio.com>, <linux-btrfs@vger.kernel.org>
Subject: Re: [PATCH] Btrfs: separate out tests into their own directory V2
Date: Fri, 30 Aug 2013 08:25:29 -0400	[thread overview]
Message-ID: <20130830122529.GH10591@localhost.localdomain> (raw)
In-Reply-To: <521FF91B.10309@cn.fujitsu.com>

On Fri, Aug 30, 2013 at 09:44:59AM +0800, Wang Shilong wrote:
> On 08/30/2013 03:29 AM, Josef Bacik wrote:
> >The plan is to have a bunch of unit tests that run when btrfs is loaded when you
> >build with the appropriate config option.  My ultimate goal is to have a test
> >for every non-static function we have, but at first I'm going to focus on the
> >things that cause us the most problems.  To start out with this just adds a
> >tests/ directory and moves the existing free space cache tests into that
> >directory and sets up all of the infrastructure.  Thanks,
> >
> >Signed-off-by: Josef Bacik <jbacik@fusionio.com>
> 
> Nothing serious, use checkpatch.pl and i get the following warnings:
> 
>  WARNING: kfree(NULL) is safe this check is probably not required
> #132: FILE: fs/btrfs/free-space-cache.c:3035:
> +    if (map)
> +        kfree(map);
> 

Good point about this, I will do it.

> WARNING: line over 80 characters
> #882: FILE: fs/btrfs/tests/free-space-tests.c:211:
> +    ret = test_add_free_space_entry(cache, 4 * 1024 * 1024, 1 * 1024 *
> 1024, 1);
> 
> WARNING: line over 80 characters
> #927: FILE: fs/btrfs/tests/free-space-tests.c:256:
> +    ret = test_add_free_space_entry(cache, 1 * 1024 * 1024, 4 * 1024 *
> 1024, 1);
> 
> WARNING: line over 80 characters
> #947: FILE: fs/btrfs/tests/free-space-tests.c:276:
> +    ret = test_add_free_space_entry(cache, 4 * 1024 * 1024, 4 * 1024 *
> 1024, 1);
> 
> WARNING: line over 80 characters
> #953: FILE: fs/btrfs/tests/free-space-tests.c:282:
> +    ret = test_add_free_space_entry(cache, 2 * 1024 * 1024, 2 * 1024 *
> 1024, 0);
> 
> WARNING: line over 80 characters
> #1016: FILE: fs/btrfs/tests/free-space-tests.c:345:
> +    ret = test_add_free_space_entry(cache, 1 * 1024 * 1024, 2 * 1024 *
> 1024, 1);
> 
> WARNING: line over 80 characters
> #1022: FILE: fs/btrfs/tests/free-space-tests.c:351:
> +    ret = test_add_free_space_entry(cache, 3 * 1024 * 1024, 1 * 1024 *
> 1024, 0);
> 
> WARNING: line over 80 characters
> #1030: FILE: fs/btrfs/tests/free-space-tests.c:359:
> +        test_msg("Error removing bitmap and extent overlapping %d\n", ret);
>

Yeah I skipped the 80 char limit in here to make the tests a little easier to
read.  Thanks,

Josef 

  reply	other threads:[~2013-08-30 12:25 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-08-29 19:29 [PATCH] Btrfs: separate out tests into their own directory V2 Josef Bacik
2013-08-30  1:44 ` Wang Shilong
2013-08-30 12:25   ` Josef Bacik [this message]
  -- strict thread matches above, loose matches on Subject: below --
2013-08-15 17:57 Josef Bacik

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=20130830122529.GH10591@localhost.localdomain \
    --to=jbacik@fusionio.com \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=wangsl.fnst@cn.fujitsu.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).