linux-kernel - Re: [PATCH 2/2] zram: permit sleeping while in pool zs

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] [day] [month] [year] [list]

Message-ID: <20121030193535.GE2454@swordfish>
Date:	Tue, 30 Oct 2012 22:35:35 +0300
From:	Sergey Senozhatsky <sergey.senozhatsky@...il.com>
To:	Greg Kroah-Hartman <gregkh@...uxfoundation.org>
Cc:	linux-kernel@...r.kernel.org
Subject: Re: [PATCH 2/2] zram: permit sleeping while in pool zs_malloc()

On (10/30/12 12:18), Greg Kroah-Hartman wrote:
> > the first one:
> > 
> > [PATCH 1/2] zram: factor-out zram_decompress_page() function
> > [PATCH 2/2] zram: handle mem suffixes in disk size zram_sysfs parameter
> > 
> > ACKed by Nitin.
> >  
> > the second one
> > 
> > [PATCH 2/2] zram: permit sleeping while in pool zs_malloc()
> > [PATCH 1/2] zram: forbid IO operations from within zram_init_device()  -- droppped by me.
> > 
> > 
> > I'll resend first two and next time will make sure not to spam your box. sorry.
> 
> Sending me lots of patches is fine, I don't mind that at all.  It's what
> I'm here for it seems :)
> 
> But when there is responses, and follow-up patches, and second versions
> and lots of other stuff, it gets hard to follow, so I ask for them all
> to be resent, like this.
> 

I'll Cc you next time only when we land the final versions.


> But, what happened with your second series?  As you didn't resend them,
> I'll just ignore them for now, please resend if you ever get them worked
> out.
> 

please ignore as I didn't have any response from Nitin yet on them. 

	-ss

> thanks,
> 
> greg k-h
> 
--
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/