linux-kernel - Re: [Q] Bio traversal trouble?

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: <466496FA.4070508@gmail.com>
Date:	Tue, 05 Jun 2007 00:49:30 +0200
From:	Rene Herman <rene.herman@...il.com>
To:	Pekka Enberg <penberg@...helsinki.fi>
CC:	Jens Axboe <jens.axboe@...cle.com>,
	Linux Kernel <linux-kernel@...r.kernel.org>
Subject: Re: [Q] Bio traversal trouble?

On 06/04/2007 10:38 PM, Rene Herman wrote:

> On 06/04/2007 08:41 PM, Pekka Enberg wrote:
> 
> [ Jens' email address updated to his oracle address ]
> 
>> We can see that we're reading 2048 bytes from port 0x300 and storing
>> the data in memory location 0x8c1d2071 which causes the OOPS. What's
>> surprising is that EBP is set to 0x8c1d2071 too which suggests stack
>> corruption (note that ioread8_rep() is a fastcall so it does not
>> create a stack frame of its own). What you could do here is add some
>> printks and watch how dst changes over time to see if you can figure
>> out a pattern.
> 
> Mmm, I do always run with 4K stacks, I guess I'll try that next.

Nope, still there with 8K stacks and not harder to trigger.

Rene.
-
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/