linux-kernel - Re: [git pull] kgdb light, v5

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

Message-ID: <20080210211347.GB29507@elte.hu>
Date:	Sun, 10 Feb 2008 22:13:47 +0100
From:	Ingo Molnar <mingo@...e.hu>
To:	Jan Kiszka <jan.kiszka@....de>
Cc:	Linus Torvalds <torvalds@...ux-foundation.org>,
	Ray Lee <ray-lk@...rabbit.org>,
	Sam Ravnborg <sam@...nborg.org>, linux-kernel@...r.kernel.org,
	Andrew Morton <akpm@....com.au>,
	Thomas Gleixner <tglx@...utronix.de>,
	Jason Wessel <jason.wessel@...driver.com>
Subject: Re: [git pull] kgdb light, v5


* Jan Kiszka <jan.kiszka@....de> wrote:

> Maybe, maybe not. I followed the comment in the original code, saying 
> that we need word-wise access for I/O memory poking. Can I assume 
> across a all archs that __copy_to/from_user will not perform byte 
> accesses if count is 2, 4, or 8? I would be glad if we can kill other 
> couple of line.

those architectures should extend mm/maccess.c accordingly. It's now the 
collector point for "weird kernel-owned memory access functionality".

> Ingo, if you are close to an editor, please pick those up? Here are 
> some offline things cooking on my side...

yeah, fixed these in my tree.

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