linux-ext4 - Re: [BUG] ext4 null pointer crash in linux-next

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: Windows password security audit tool. GUI, reports in PDF.

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

Message-ID: <839b29df-08af-403c-da3e-e1bc9eca1685@acm.org>
Date:   Mon, 8 Oct 2018 20:41:15 -0700
From:   Bart Van Assche <bvanassche@....org>
To:     valdis.kletnieks@...edu, Theodore Ts'o <tytso@....edu>,
        Andreas Dilger <adilger.kernel@...ger.ca>,
        Jens Axboe <axboe@...nel.dk>
Cc:     linux-kernel@...r.kernel.org, linux-ext4@...r.kernel.org,
        linux-block@...r.kernel.org
Subject: Re: [BUG] ext4 null pointer crash in linux-next

On 10/8/18 12:54 PM, valdis.kletnieks@...edu wrote:
> [  680.692915] RIP: 0010:__get_request+0x31/0x7e0

Can you provide the source code line number that corresponds to that 
address? If you haven't done this before: enter gdb 
${path_to_kernel_source_tree}/vmlinux in a shell and then run "list 
*(__get_request+0x31)" (without the double quotes).

Additionally, which block driver is being used in your setup under the 
ext4 filesystem?

Thanks,

Bart.