linux-kernel - Re: [RFC][PATCH 7/8] Convert sparc to use arch

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

Date:	Tue, 14 Apr 2009 19:51:35 -0700 (PDT)
From:	David Miller <davem@...emloft.net>
To:	johnstul@...ibm.com
Cc:	linux-kernel@...r.kernel.org, rmk+lkml@....linux.org.uk,
	cooloney@...nel.org, starvik@...s.com, takata@...ux-m32r.org,
	geert@...ux-m68k.org, zippel@...ux-m68k.org, lethal@...ux-sh.org,
	magnus.damm@...il.com, wli@...omorphy.com, rth@...ddle.net
Subject: Re: [RFC][PATCH 7/8] Convert sparc to use arch_getoffset()
 infrastructure.

From: john stultz <johnstul@...ibm.com>
Date: Tue, 14 Apr 2009 18:51:26 -0700

> 	You acked this patch earlier, but I've just tried building with a
> cross-compiler environment I had access to and had problems getting it
> to build.
> 
> It seems the pci_do_get/settimeofday() and the bus_do_get/settimeofday()
> redirection code is causing some trouble. I'm really not sure how the
> BTFIXUPSET_CALL code works, so I don't want to just kill it off. 
> 
> Any advice here on how to do this right?

BTFIXUP is basically a kernel boot time patching service, but
it only works if we can declare function prototypes in the
sparc specific header files.

Since do_gettimeofday() doesn't fall into that requirement, the code
in pci_time_init() is patching the first two instructions of
do_gettimeofday() such that is makes a call to pci_do_gettimeofday().
--
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/