linux-kernel - Re: Linux 2.6.23

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]

Date:	Wed, 10 Oct 2007 21:14:13 +0200
From:	Ingo Molnar <mingo@...e.hu>
To:	René Rebe <rene@...ctcode.de>
Cc:	Linus Torvalds <torvalds@...ux-foundation.org>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: Linux 2.6.23


* René Rebe <rene@...ctcode.de> wrote:

> Hi Linus et al.,
> 
> 2.6.23 does not build with my usual .config on x86_64 and gcc-4.2.1:

i know about 4 (low-impact, cornercase) build breakages for 2.6.23-final 
on x86:

- an uncommon embedded config combinatio: if CONFIG_EMBEDDED=y and
  CONFIG_BLOCK is unset. (a normally useless combination)

- an uncommon V4L config combination: mixed-modular-built-in driver V4L
  config variation. (CONFIG_VIDEO_SAA7146=y and CONFIG_VIDEO_BUF=m)

- an uncommon MTD config combination (normal systems do not need
  CONFIG_MTD configured)

- an uncommon CONFIG_USB_NET_CDC_SUBSET config combination (normal 
  systems should never hit that)

[ furthermore there are a few driver-firmware build options that break 
  and which are not correctly made dependent on !PREVENT_FIRMWARE_BUILD. 
  Again, this is not something one would normally configure. ]

your superblock build failure would be a new and so far unknown build 
breakage variant - please send the .config you used, and double-check 
that it's indeed a vanilla 2.6.23 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/