linux-kernel - Re: [mainline][BUG][PPC][btrfs][bisected 00801a] kernel BUG at fs/btrfs/locking.c:71!

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:   Wed, 11 Sep 2019 11:09:34 +0300
From:   Nikolay Borisov <nborisov@...e.com>
To:     Abdul Haleem <abdhalee@...ux.vnet.ibm.com>
Cc:     mpe <mpe@...erman.id.au>, Brian King <brking@...ux.vnet.ibm.com>,
        chandan <chandan@...ux.vnet.ibm.com>,
        sachinp <sachinp@...ux.vnet.ibm.com>,
        linuxppc-dev <linuxppc-dev@...ts.ozlabs.org>,
        David Sterba <dsterba@...e.com>, josef@...icpanda.com,
        linux-btrfs@...r.kernel.org,
        linux-kernel <linux-kernel@...r.kernel.org>
Subject: Re: [mainline][BUG][PPC][btrfs][bisected 00801a] kernel BUG at
 fs/btrfs/locking.c:71!



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.