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-next>] [day] [month] [year] [list]
Date:	Tue, 25 Oct 2011 15:04:53 +0200
From:	Sedat Dilek <sedat.dilek@...glemail.com>
To:	Stephen Rothwell <sfr@...b.auug.org.au>,
	Jens Axboe <axboe@...nel.dk>
Cc:	linux-next@...r.kernel.org, LKML <linux-kernel@...r.kernel.org>,
	Linus <torvalds@...ux-foundation.org>
Subject: Re: linux-next: Tree for Oct 25 (block ?)

On Tue, Oct 25, 2011 at 11:36 AM, Stephen Rothwell <sfr@...b.auug.org.au> wrote:
> Hi all,
>
> *Note well*
>
> This tree has nate had any build testing at all.  As such, it probably
> doesn't build :-) This tree is really just a roll up of the current state
> of the trees when the v3.2 merge window opened.  It will not be put into
> the build system referred to below.
>

I have generated a single linux-next (next-20111025) patch on top of
v3.1, it's approx. 100M!

$ du -h patch-v3.1-next-20111025.patch
96M     patch-v3.1-next-20111025.patch

I noticed this build-failure:

  CC      block/blk-throttle.o
  CC [M]  fs/fuse/dir.o
/mnt/sdb3/linux-kernel/linux-3.1/debian/build/source_i386_none/block/blk-throttle.c:
In function 'blk_throtl_drain':
/mnt/sdb3/linux-kernel/linux-3.1/debian/build/source_i386_none/block/blk-throttle.c:1221:2:
error: implicit declaration of function 'lockdep_is_held'
[-Werror=implicit-function-declaration]
cc1: some warnings being treated as errors

make[5]: *** [block/blk-throttle.o] Error 1
make[4]: *** [block] Error 2

This happens with Debian's gcc-4.6 (4.6.1-16) and default
KBUILD_ENABLE_EXTRA_GCC_CHECKS value.

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