From: Nikolay Borisov <nborisov@suse.com>
To: Abdul Haleem <abdhalee@linux.vnet.ibm.com>
Cc: sachinp <sachinp@linux.vnet.ibm.com>,
josef@toxicpanda.com, linux-kernel <linux-kernel@vger.kernel.org>,
David Sterba <dsterba@suse.com>,
chandan <chandan@linux.vnet.ibm.com>,
Brian King <brking@linux.vnet.ibm.com>,
linuxppc-dev <linuxppc-dev@lists.ozlabs.org>,
linux-btrfs@vger.kernel.org
Subject: Re: [mainline][BUG][PPC][btrfs][bisected 00801a] kernel BUG at fs/btrfs/locking.c:71!
Date: Wed, 11 Sep 2019 11:09:34 +0300 [thread overview]
Message-ID: <c51e672f-c5b2-13d9-afa4-8f44a1e8580a@suse.com> (raw)
In-Reply-To: <1568188807.30609.6.camel@abdul.in.ibm.com>
On 11.09.19 г. 11:00 ч., Abdul Haleem wrote:
> On Tue, 2019-09-03 at 13:39 +0300, Nikolay Borisov wrote:
>>
<split>
>> corresponds to?
>
> btrfs_search_slot+0x8e8/0xb80 maps to fs/btrfs/ctree.c:2751
> write_lock_level = BTRFS_MAX_LEVEL;
That doesn't make sense, presumably btrfs_search_slot+0x8e8/0xb80 should
point at or right after the instruction which called
btrfs_set_path_blocking. So either line 2796, 2894, 2901 or 2918 .
> 9a70: 08 00 40 39 li r10,8
> 9a74: 08 00 a0 3a li r21,8
>> 9a78: 6c 00 41 91 stw r10,108(r1)
> 9a7c: 1c f8 ff 4b b 9298 <btrfs_search_slot+0x108>
> b = btrfs_root_node(root);
>
>
> and btrfs_assert_tree_locked+0x10/0x20 maps to ./fs/btrfs/locking.c:71
>
> void btrfs_assert_tree_locked(struct extent_buffer *eb)
> {
> BUG_ON(!eb->write_locks);
> 80: 14 01 23 81 lwz r9,276(r3)
> 84: 34 00 29 7d cntlzw r9,r9
> 88: 7e d9 29 55 rlwinm r9,r9,27,5,31
> 8c: 20 00 29 79 clrldi r9,r9,32
>> 90: 00 00 09 0b tdnei r9,0
> 94: 20 00 80 4e blr
> 98: 00 00 00 60 nop
> 9c: 00 00 42 60 ori r2,r2,0
>
> I have sent direct message attaching vmlinux and the obj dump for
> ctree.c and locking.c
>
I just got a message from : InterScan Messaging Security Suite about
some policy being broken and no vmscan.
next prev parent reply other threads:[~2019-09-11 8:11 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-03 8:55 [mainline][BUG][PPC][btrfs][bisected 00801a] kernel BUG at fs/btrfs/locking.c:71! Abdul Haleem
2019-09-03 10:39 ` Nikolay Borisov
2019-09-11 8:00 ` Abdul Haleem
2019-09-11 8:09 ` Nikolay Borisov [this message]
2019-09-11 9:14 ` Abdul Haleem
2019-09-03 12:38 ` David Sterba
2019-09-06 15:51 ` 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=c51e672f-c5b2-13d9-afa4-8f44a1e8580a@suse.com \
--to=nborisov@suse.com \
--cc=abdhalee@linux.vnet.ibm.com \
--cc=brking@linux.vnet.ibm.com \
--cc=chandan@linux.vnet.ibm.com \
--cc=dsterba@suse.com \
--cc=josef@toxicpanda.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=sachinp@linux.vnet.ibm.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).