All of lore.kernel.org
 help / color / mirror / Atom feed
From: David Sterba <dsterba@suse.cz>
To: Nikolay Borisov <nborisov@suse.com>
Cc: Qu Wenruo <wqu@suse.com>, linux-btrfs@vger.kernel.org, dsterba@suse.cz
Subject: Re: [PATCH v2] btrfs-progs: free-space-cache: Enhance free space cache free space check
Date: Fri, 9 Mar 2018 16:48:04 +0100	[thread overview]
Message-ID: <20180309154804.GU23693@twin.jikos.cz> (raw)
In-Reply-To: <990e0fd3-eb5a-8036-18c8-b88c3af1c0bf@suse.com>

On Fri, Mar 09, 2018 at 10:06:02AM +0200, Nikolay Borisov wrote:
> >>> +		 * space cache has less free space, and both kernel just discard
> >>> +		 * such cache. But if we find some case where free space cache
> >>> +		 * has more free space, this means under certain case such
> >>> +		 * cache can be loaded and cause double allocate.
> >>> +		 *
> >>> +		 * Detect such possibility here.
> >>> +		 */
> >>> +		if (diff > 0)
> >>> +			error(
> >>> +"free space cache has more free space than block group item, this could leads to serious corruption, please contact btrfs developers");
> >>
> >> I'm not entirely happy with this message. So they will post to the
> >> mailing list saying something along the lines of "I got this message
> >> what do I do no, please help".  Better to output actionable data so that
> >> the user can post it immediately.
> > 
> > Unfortunately, this is already the situation we don't expect to see.
> > 
> > What we really need is to know this could happen, and if possible some
> > info about the situation.
> > There is not much actionable data here.
> 
> Fair enough, at the very least I think we should put information how to
> contact btrfs developers. So put the address of the mailing list, I
> don't think it's safe to assume people will be aware of it .

This should go to the manual page or help string, and reference it from
here.

  reply	other threads:[~2018-03-09 15:50 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-03-08  7:02 [PATCH v2] btrfs-progs: free-space-cache: Enhance free space cache free space check Qu Wenruo
2018-03-08 14:05 ` Nikolay Borisov
2018-03-08 23:27   ` Qu Wenruo
2018-03-09  8:06     ` Nikolay Borisov
2018-03-09 15:48       ` David Sterba [this message]
2018-03-09 15:49 ` 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=20180309154804.GU23693@twin.jikos.cz \
    --to=dsterba@suse.cz \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=nborisov@suse.com \
    --cc=wqu@suse.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.