From: Johannes Thumshirn <Johannes.Thumshirn@wdc.com>
To: Qu Wenruo <quwenruo.btrfs@gmx.com>,
"dsterba@suse.cz" <dsterba@suse.cz>,
David Sterba <dsterba@suse.com>
Cc: "linux-btrfs@vger.kernel.org" <linux-btrfs@vger.kernel.org>
Subject: Re: Bug 5.7-rc: root leak, eb leak
Date: Wed, 13 May 2020 12:06:07 +0000 [thread overview]
Message-ID: <SN4PR0401MB3598875C33493DDC0D8BA60D9BBF0@SN4PR0401MB3598.namprd04.prod.outlook.com> (raw)
In-Reply-To: fa11e7ec-d785-455e-02f9-c45d607c0b52@gmx.com
On 13/05/2020 13:57, Qu Wenruo wrote:
>
>
> On 2020/5/13 下午7:54, Johannes Thumshirn wrote:
>> On 13/05/2020 01:04, David Sterba wrote:
>> [...]
>>>
>>> Johannes, do you have logs from the test?
>>
>>
>>
>> I recreated the logs for btrfs/028 (dmesg, kmemleak and fstests log). Please find them attached.
>>
>
> BTW, what's the line of open_ctree+0x137c/0x277a?
Here we go:
(gdb) l *(open_ctree+0x137c/0x277a)
0x122acd is in open_ctree (fs/btrfs/disk-io.c:2826).
2821 u64 generation;
2822 u64 features;
2823 u16 csum_type;
2824 struct btrfs_key location;
2825 struct btrfs_super_block *disk_super;
2826 struct btrfs_fs_info *fs_info = btrfs_sb(sb);
2827 struct btrfs_root *tree_root;
2828 struct btrfs_root *chunk_root;
2829 int ret;
2830 int err = -EINVAL;
So its:
2826 struct btrfs_fs_info *fs_info = btrfs_sb(sb);
next prev parent reply other threads:[~2020-05-13 12:06 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-12 14:12 Pending bugs for 5.7 David Sterba
2020-05-12 14:14 ` Bug 5.7-rc: root leak, eb leak David Sterba
2020-05-12 23:03 ` David Sterba
2020-05-13 11:54 ` Johannes Thumshirn
2020-05-13 11:57 ` Qu Wenruo
2020-05-13 12:06 ` Johannes Thumshirn [this message]
2020-05-13 12:11 ` Qu Wenruo
2020-05-13 12:17 ` Johannes Thumshirn
2020-05-13 12:29 ` Johannes Thumshirn
2020-05-12 14:15 ` Bug 5.7-rc: write-time leaf corruption detected David Sterba
2020-05-12 14:26 ` Filipe Manana
2020-05-13 3:10 ` Qu Wenruo
2020-05-13 3:17 ` Qu Wenruo
2020-05-13 9:25 ` Filipe Manana
2020-05-19 14:26 ` Bug 5.7-rc: write-time leaf corruption detected (fixed) David Sterba
2020-05-12 14:15 ` Bug 5.7-rc: lockdep warning, chunk_mutex/device_list_mutex David Sterba
2020-05-12 23:28 ` David Sterba
2020-05-12 19:25 ` Anand Jain
2020-05-13 19:46 ` [PATCH] btrfs: fix lockdep warning chunk_mutex vs device_list_mutex Anand Jain
2020-05-15 17:40 ` David Sterba
2020-05-16 3:43 ` Anand Jain
2020-05-18 11:07 ` Anand Jain
2020-05-18 15:28 ` David Sterba
2020-05-12 14:15 ` Bug 5.7-rc: lockdep warning, fs_reclaim 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=SN4PR0401MB3598875C33493DDC0D8BA60D9BBF0@SN4PR0401MB3598.namprd04.prod.outlook.com \
--to=johannes.thumshirn@wdc.com \
--cc=dsterba@suse.com \
--cc=dsterba@suse.cz \
--cc=linux-btrfs@vger.kernel.org \
--cc=quwenruo.btrfs@gmx.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).