All of lore.kernel.org
 help / color / mirror / Atom feed
From: Liu Bo <bo.li.liu@oracle.com>
To: David Sterba <dsterba@suse.cz>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: [PATCH] Btrfs: fix off-by-one in lseek
Date: Thu, 10 Jan 2013 21:34:37 +0800	[thread overview]
Message-ID: <20130110133436.GB3616@liubo> (raw)
In-Reply-To: <20130110110458.GA20089@twin.jikos.cz>

On Thu, Jan 10, 2013 at 12:04:58PM +0100, David Sterba wrote:
> On Thu, Jan 10, 2013 at 10:17:49AM +0800, Liu Bo wrote:
> > Thanks for the report, could you please show me what options you're
> > using?
> 
> Default mkfs, mount options 'space_cache,noatime', 40G test partition,
> 10G scratch partition (ie. the same seatup as usual).
> 
> I see the free_fs_root warning only 3 times in the whole serial console
> log, the first matches the first run and report, the two other are from
> a repeated run of xfstests (I don't know which options were on during
> the third, but can let it run again if needed).
> 
> This strongly suggests that the warning is connected to the fixes.

Seems that I'm not able to reproduce the warning in running 013,
maybe you can revert the two fixes and see if it still warns?

I don't think the fixes has anything done with the warning...

thanks,
liubo

  reply	other threads:[~2013-01-10 13:37 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-07  3:53 [PATCH] Btrfs: fix off-by-one in lseek Liu Bo
2013-01-07 16:20 ` David Sterba
2013-01-08  2:46   ` Liu Bo
2013-01-08  8:30     ` David Sterba
2013-01-08 17:26       ` David Sterba
2013-01-09  4:34         ` Liu Bo
2013-01-09 11:50           ` David Sterba
2013-01-09 12:49             ` David Sterba
2013-01-10  2:17             ` Liu Bo
2013-01-10 11:04               ` David Sterba
2013-01-10 13:34                 ` Liu Bo [this message]
2013-01-11 15:25                   ` David Sterba
2013-01-11 17:49                     ` David Sterba
2013-04-30 14:28           ` David Sterba

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=20130110133436.GB3616@liubo \
    --to=bo.li.liu@oracle.com \
    --cc=dsterba@suse.cz \
    --cc=linux-btrfs@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.