All of lore.kernel.org
 help / color / mirror / Atom feed
From: Qu Wenruo <quwenruo.btrfs@gmx.com>
To: Hans van Kranenburg <hans.van.kranenburg@mendix.com>,
	Steve Leung <sjleung@shaw.ca>,
	linux-btrfs@vger.kernel.org
Subject: Re: off-by-one uncompressed invalid ram_bytes corruptions
Date: Tue, 5 Jun 2018 13:24:49 +0800	[thread overview]
Message-ID: <d3fa0409-81b0-958d-e0b1-be637cff2c01@gmx.com> (raw)
In-Reply-To: <c0ff94a7-2465-ef57-9aab-09d8adf7c8f1@mendix.com>


[-- Attachment #1.1: Type: text/plain, Size: 731 bytes --]



On 2018年05月30日 02:49, Hans van Kranenburg wrote:
> On 05/21/2018 03:07 AM, Qu Wenruo wrote:
>>
>> [...]
>>
>> And the problem of wrong "root=" output also makes me pretty curious.
> Yeah, there a bunch of error messages in the kernel with always say
> root=1, regardless of the actual root the tree block is in.

I think the problem is already fixed in latest kernel.

The original version is using inode->root, which is always pointing to
root tree.

In my testing VM using 4.17-rc5, it's showing the correct value.

If you still find such problem, feel free to report it.

Thanks,
Qu

> 
> I think I once tried to find out why, but apparently it wasn't a really
> obvious error somewhere.
> 


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

      reply	other threads:[~2018-06-05  5:25 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-18  5:23 off-by-one uncompressed invalid ram_bytes corruptions Steve Leung
2018-05-18  5:49 ` Qu Wenruo
2018-05-18  9:42   ` james harvey
2018-05-18  9:56     ` Qu Wenruo
2018-05-19 23:40   ` Steve Leung
2018-05-20  1:02     ` Qu Wenruo
2018-05-20 20:43       ` Steve Leung
2018-05-21  1:07         ` Qu Wenruo
2018-05-26 14:06           ` Steve Leung
2018-05-27  0:57             ` Qu Wenruo
2018-05-28  3:47               ` Steve Leung
2018-05-28  5:11                 ` Qu Wenruo
2018-05-29 14:58                   ` Steve Leung
2018-06-05  5:30                     ` Qu Wenruo
2018-06-06  4:06                       ` Steve Leung
2018-05-29 18:49           ` Hans van Kranenburg
2018-06-05  5:24             ` Qu Wenruo [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=d3fa0409-81b0-958d-e0b1-be637cff2c01@gmx.com \
    --to=quwenruo.btrfs@gmx.com \
    --cc=hans.van.kranenburg@mendix.com \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=sjleung@shaw.ca \
    /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.