linux-kernel - [PATCH 0/1 ] fs: Warming in _

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>] [day] [month] [year] [list]

Message-ID: <a1c9e590-2d42-23bc-bdf7-3f3c784284b5@gmail.com>
Date:   Wed, 16 Aug 2023 22:10:14 +0530
From:   Manas Ghandat <ghandatmanas@...il.com>
To:     viro@...iv.linux.org.uk, brauner@...nel.org
Cc:     linux-fsdevel@...r.kernel.org, linux-kernel@...r.kernel.org,
        Linux-kernel-mentees@...ts.linuxfoundation.org
Subject: [PATCH 0/1 ] fs: Warming in __brelse

Hi,

I was working on the following syzbot bug:

https://syzkaller.appspot.com/bug?extid=ce3af36144a13b018cc7

Upon debugging I found that in this case the buffer_head is having count 
0 and then when __brelse is called it tries to free it. A simple 
solution to this problem would be to remove the warn call. SInce in any 
case the buffers only get freed if the count is present and consequently 
the pointers are also set to null. Additionally we could add a check in 
the has_bh_in_lru to also consider the counter.

Link : 
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/fs/buffer.c?id=d192f5382581d972c4ae1b4d72e0b59b34cadeb9#n1509