linux-kernel - Re: [GIT PULL] ext4 fixes

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:	Sat, 24 Apr 2010 20:53:36 -0400
From:	tytso@....edu
To:	Linus Torvalds <torvalds@...ux-foundation.org>
Cc:	linux-ext4@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [GIT PULL] ext4 fixes

Ping?  

I'm guessing that perhaps you didn't pull because of concerns raised
about some of the crazy dates in the ext4 tree.  I've checked to make
sure this isn't true for this set of patches, and I'll make sure the
dates are well-behaved for the future.

Best regards,

     	       	   	     		  - Ted

On Tue, Apr 20, 2010 at 05:39:28PM -0400, Theodore Ts'o wrote:
> Hi Linus,
> 
> I have some fixes for some data corruption bugs that should really get
> pulled into the 2.6.34 kernel, so I'd appreciate it if you could pull
> from:
> 
>         git://git.kernel.org/pub/scm/linux/kernel/git/tytso/ext4.git for_linus
> 
> Thanks,
> 
> 						- Ted
> 
>  fs/ext4/extents.c |    1 +
>  fs/ext4/inode.c   |    3 ++-
>  fs/ext4/mballoc.c |   21 +++++++++++----------
>  3 files changed, 14 insertions(+), 11 deletions(-)
> 
> Curt Wohlgemuth (2):
>       ext4: Fix possible lost inode write in no journal mode
>       ext4: Fix buffer head leaks after calls to ext4_get_inode_loc()
> 
> Theodore Ts'o (1):
>       ext4: Issue the discard operation *before* releasing the blocks to be reused
> 
> 
> 
--
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/