linux-kernel - Re: [RFC][PATCH -mm 0/5] swsusp: Fix handling of highmem

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:	Wed, 9 Aug 2006 21:52:10 +1000
From:	Nigel Cunningham <ncunningham@...uxmail.org>
To:	Pavel Machek <pavel@...e.cz>
Cc:	"Rafael J. Wysocki" <rjw@...k.pl>,
	LKML <linux-kernel@...r.kernel.org>, Linux PM <linux-pm@...l.org>
Subject: Re: [RFC][PATCH -mm 0/5] swsusp: Fix handling of highmem

On Wednesday 09 August 2006 21:38, Pavel Machek wrote:
> Hi!
>
> > > Comments welcome.
> >
> > Thanks for the reminder. I'd forgotten half the reason why I didn't want
> > to make Suspend2 into incremental patches! You're a brave man!
>
> Why does this serve as a reminder? No, it is not easy to merge big
> patches to mainline. But it is actually a feature.

It serves as a reminder because it shows (just the description, I mean), how 
inter-related all the changes that are needed are.

I don't get the "it is actually a feature" bit.

> > while (1) {
> >   size=$RANDOM * 65536 + 1
> >   dd if=/dev/random bs=1 count=$size | patch -p0-b
> >   make && break
> >}
>
> Is this what you use to generate suspend2 patches? :-)))))

:) Actually, given Greg's OLS keynote, I was wondering if it was what he used 
to generate them.

Regards,

Nigel
-- 
Nigel, Michelle and Alisdair Cunningham
5 Mitchell Street
Cobden 3266
Victoria, Australia

Content of type "application/pgp-signature" skipped