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:	Mon, 13 May 2013 14:54:52 +0200
From:	Hans-Christian Egtvedt <egtvedt@...fundet.no>
To:	Geert Uytterhoeven <geert@...ux-m68k.org>
Cc:	Linux Kernel Development <linux-kernel@...r.kernel.org>,
	Haavard Skinnemoen <hskinnemoen@...il.com>
Subject: Re: Build regressions/improvements in v3.10-rc1 (avr)

Around Sun 12 May 2013 22:45:01 +0200 or thereabout, Geert Uytterhoeven wrote:
> On Sun, 12 May 2013, Geert Uytterhoeven wrote:
>> However, the full list of errors isn't that unmanageable, so I'm following
>> up with a digested list...
> 
> (.init.text+0x540): undefined reference to `atmel_default_console_device': 1 errors in 1 logs
> 	v3.10-rc1/avr32/avr32-allnoconfig
> 	Patch sent last February

I recall to have acked patch(es) related to the serial (console) driver.

It is caused by CONFIG_SERIAL_ATMEL no set in .config, but the machine code
still writes to atmel_default_console_device when you call
at32_setup_serial_console().

Two ways to fix, either select the SERIAL_ATMEL symbol or ifdef around the
atmel_default_console_device assignment in the machine code.

> vsprintf.c:(.text+0x8de): relocation truncated to fit: R_AVR32_9UW_PCREL against `.text'+ae0: 1 errors in 1 logs
> 	v3.10-rc1/avr32/avr32-allnoconfig

I suspect this is caused by not optimizing for size.

-- 
mvh
Hans-Christian Egtvedt
--
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/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ