linux-kernel - Re: Linux 2.6.34-rc1

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]

Message-ID: <20100309162804.GB7373@atrey.karlin.mff.cuni.cz>
Date:	Tue, 9 Mar 2010 17:28:04 +0100
From:	Jan Kara <jack@...e.cz>
To:	Linus Torvalds <torvalds@...ux-foundation.org>
Cc:	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: Linux 2.6.34-rc1

> It's out there now. I still have a few trees I already got pull requests 
> for, and that I want to look over a bit more (ceph, gdb tree etc), and 
> it's possible that I've just overlooked some other pull request.
  It seems you haven't pulled my UDF tree (requested on Thursday -
http://lkml.indiana.edu/hypermail/linux/kernel/1003.0/02186.html).
  I've rebased the tree on top of 2.6.34-rc1 so could you please pull
now?
  The full pull request for your convenience:

  could you please pull from

git://git.kernel.org/pub/scm/linux/kernel/git/jack/linux-udf-2.6.git for_linus

  to get:

Akinobu Mita (1):
      udf: use ext2_find_next_bit

Jan Kara (2):
      udf: Fix unalloc space handling in udf_update_inode
      udf: Do not read inode before writing it

The diffstat is

 fs/udf/balloc.c |   49 +------------------------------------------------
 fs/udf/inode.c  |   34 +++++++++++++++++-----------------
 2 files changed, 18 insertions(+), 65 deletions(-)

								Honza
-- 
Jan Kara <jack@...e.cz>
SuSE CR Labs
--
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/