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  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:	Sun, 23 Nov 2008 19:29:29 +0530
From:	"Aneesh Kumar K.V" <>
To:	Theodore Tso <tytso@....EDU>
Subject: Re: [PATCH -V2 2/5] ext4: unlock group before ext4_error

On Sun, Nov 23, 2008 at 08:43:04AM -0500, Theodore Tso wrote:
> On Sun, Nov 23, 2008 at 08:37:04AM -0500, Theodore Tso wrote:
> > This looks like it came from the patch
> > aneesh-8-fix-double-free-of-blocks which in a message sent roughly at
> > the same time you told me to drop from the patch queue.  So I'm adding
> > this to the patch queue without this rejected hunk.
> Sorry, I managed to confuse myself.  The patch conflict went away
> after I removed the patch per your e-mail.  I have so many *.rej files
> in my tree from failed patches that I managed to confuse myself.  I'll
> have to clean them out....
> My comments about how difficult it is to figure out where your patches
> apply are still relevant......  I'm still trying to figure this all
> out, but you'll need to check the patch queue afterwards.  Can you
> please give me a status readout about which patches I can move into
> the stable part of the tree, please?  And what the status is of the
> other patches?  Thanks!!!

All the patches I do are mostly after applying all the patches in the
patch queue. I would wait for some review and wider testing
on the patches before they can be moved to stable part of the
patch queue.

To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
the body of a message to
More majordomo info at

Powered by blists - more mailing lists