linux-kernel - Re: C aggregate passing (Rust kernel policy)

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: <20250302121957.28f08504@pumpkin>
Date: Sun, 2 Mar 2025 12:19:57 +0000
From: David Laight <david.laight.linux@...il.com>
To: Steven Rostedt <rostedt@...dmis.org>
Cc: Kent Overstreet <kent.overstreet@...ux.dev>, James Bottomley
 <James.Bottomley@...senpartnership.com>, Greg KH
 <gregkh@...uxfoundation.org>, Miguel Ojeda
 <miguel.ojeda.sandonis@...il.com>, Ventura Jack <venturajack85@...il.com>,
 "H. Peter Anvin" <hpa@...or.com>, Alice Ryhl <aliceryhl@...gle.com>, Linus
 Torvalds <torvalds@...ux-foundation.org>, Gary Guo <gary@...yguo.net>,
 airlied@...il.com, boqun.feng@...il.com, hch@...radead.org,
 ksummit@...ts.linux.dev, linux-kernel@...r.kernel.org,
 rust-for-linux@...r.kernel.org, Ralf Jung <post@...fj.de>, Josh Poimboeuf
 <jpoimboe@...hat.com>
Subject: Re: C aggregate passing (Rust kernel policy)

On Wed, 26 Feb 2025 12:47:33 -0500
Steven Rostedt <rostedt@...dmis.org> wrote:

> On Wed, 26 Feb 2025 12:41:30 -0500
> Kent Overstreet <kent.overstreet@...ux.dev> wrote:
> 
> > It's been awhile since I've looked at one, I've been just automatically
> > switching back to frame pointers for awhile, but - I never saw
> > inaccurate backtraces, just failure to generate a backtrace - if memory
> > serves.  
> 
> OK, maybe if the bug was bad enough, it couldn't get access to the ORC
> tables for some reason. Not having a backtrace on crash is not as bad as
> incorrect back traces, as the former is happening when the system is dieing
> and live kernel patching doesn't help with that.

I bet to differ.
With no backtrace you have absolutely no idea what happened.
A list of 'code addresses on the stack' (named as such) can be enough
to determine the call sequence.
Although to be really helpful you need a hexdump of the actual stack
and the stack addresses of each 'code address'.

	David