linux-kernel - Re: PROBLEM: 2.6.19 + highmem = BUG at do_wp

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

Message-ID: <20061229204147.GA3844@m.safari.iki.fi>
Date:	Fri, 29 Dec 2006 22:41:47 +0200
From:	Sami Farin <7atbggg02@...akemail.com>
To:	linux-kernel@...r.kernel.org
Cc:	Chuck Ebbert <76306.1226@...puserve.com>,
	Andrew Morton <akpm@...l.org>
Subject: Re: PROBLEM: 2.6.19 + highmem = BUG at do_wp_page

On Tue, Dec 12, 2006 at 15:10:56 -0500, Chuck Ebbert wrote:
> In-Reply-To: <20061205172512.GA5518@...afari.iki.fi>
> 
> On Tue, 5 Dec 2006 19:25:13 +0200, Sami Farin wrote:
> 
> > BUG: unable to handle kernel paging request at virtual address fffb9dc0
> 
> > eax: fffb8000   ebx: fffb9000   ecx: 00000090   edx: 00000000
> > esi: fffb9dc0   edi: fffb8dc0   ebp: f6f89f24   esp: f6f89ef0
> 
>   1f:   89 de                     mov    %ebx,%esi
>   21:   b9 00 04 00 00            mov    $0x400,%ecx
>   26:   89 45 cc                  mov    %eax,0xffffffcc(%ebp)
>   29:   89 c7                     mov    %eax,%edi
> 
>    0:   f3 a5                     repz movsl %ds:(%esi),%es:(%edi)   <=====
> 
> Processor started to copy a page, then with 576 bytes left to copy
> the source page got unmapped.  Nice.
> 
> This possibly happened during a device interrupt. What does
> /proc/interrupts say?

My system now works with HIGHMEM (got 103 MB extra mem for use).

I Fixed™ this by nuking crypto API out of the fortuna patch
and including my own functions...

$ cat /proc/sys/kernel/random/cipher_algo 
Snuffle 2005

hehe..

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