linux-kernel - frame unwinder patches

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

Date:	Thu, 04 Sep 2008 18:46:52 +0200
From:	Bernd Schubert <bs@...eap.de>
To:	linux-kernel@...r.kernel.org
Subject:  frame unwinder patches

Hello,

up to 2.6.22 the -mm series had these nice frame unwinder patches, 
which gave beautiful stack traces. Unfortunately these frame unwinder patches
seem to have been dropped :(

Anyone still maintaining updated patches?

Here is an example of a horrible stack trace, confusing my eyes

[  855.504734] Call Trace:
[  855.504734]  [<ffffffff80495af2>] ? scsi_request_fn+0x252/0x370
[  855.504734]  [<ffffffff8058b068>] io_schedule+0x28/0x40
[  855.504734]  [<ffffffff8038b876>] get_request_wait+0x96/0x110
[  855.504734]  [<ffffffff80249d40>] ? autoremove_wake_function+0x0/0x40
[  855.504734]  [<ffffffff8038bca8>] blk_get_request+0x38/0x80
[  855.504734]  [<ffffffff804950a3>] scsi_execute+0x43/0x140
[  855.504734]  [<ffffffffa00250dc>] :scsi_transport_spi:spi_execute+0x7c/0xd0
[  855.504734]  [<ffffffff8038accb>] ? blk_put_request+0x4b/0x60
[  855.504734]  [<ffffffff8049515f>] ? scsi_execute+0xff/0x140
[  855.504734]  [<ffffffffa0025b86>] :scsi_transport_spi:spi_dv_device_echo_buffer+0x1c6/0x290
[  855.504734]  [<ffffffffa00349f0>] ? :mptbase:mpt_timer_expired+0x0/0x70
[  855.504734]  [<ffffffffa0024dc3>] :scsi_transport_spi:spi_dv_retrain+0x63/0x240
[  855.504734]  [<ffffffffa00259c0>] ? :scsi_transport_spi:spi_dv_device_echo_buffer+0x0/0x290
[  855.504734]  [<ffffffffa00255f7>] :scsi_transport_spi:spi_dv_device+0x3b7/0x720
[  855.504734]  [<ffffffffa005017b>] :mptspi:mptspi_dv_device+0x6b/0x1a0
[  855.504734]  [<ffffffffa00502ce>] ? :mptspi:mptspi_dv_renegotiate_work+0x1e/0x100
[  855.504734]  [<ffffffffa005038f>] :mptspi:mptspi_dv_renegotiate_work+0xdf/0x100
[  855.504734]  [<ffffffffa00502b0>] ? :mptspi:mptspi_dv_renegotiate_work+0x0/0x100
[  855.504734]  [<ffffffffa00502b0>] ? :mptspi:mptspi_dv_renegotiate_work+0x0/0x100
[  855.504734]  [<ffffffff80245b36>] run_workqueue+0x176/0x220
[  855.504734]  [<ffffffff80246786>] worker_thread+0xa6/0x110
[  855.504734]  [<ffffffff80249d40>] ? autoremove_wake_function+0x0/0x40
[  855.504734]  [<ffffffff802466e0>] ? worker_thread+0x0/0x110
[  855.504734]  [<ffffffff8024990d>] kthread+0x4d/0x80
[  855.504734]  [<ffffffff8020c5e8>] child_rip+0xa/0x12
[  855.504734]  [<ffffffff8020bcff>] ? restore_args+0x0/0x30
[  855.504734]  [<ffffffff802498c0>] ? kthread+0x0/0x80
[  855.504734]  [<ffffffff8020c5de>] ? child_rip+0x0/0x12
[  855.504734]

Probably all the "?" lines shouldn't be printed.


Thanks,
Bernd

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/