[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20110706012739.GA32221@outflux.net>
Date: Tue, 5 Jul 2011 18:27:39 -0700
From: Kees Cook <kees.cook@...onical.com>
To: "H. Peter Anvin" <hpa@...or.com>
Cc: x86@...nel.org, linux-kernel@...r.kernel.org,
Len Brown <len.brown@...el.com>, Pavel Machek <pavel@....cz>,
"Rafael J. Wysocki" <rjw@...k.pl>,
Thomas Gleixner <tglx@...utronix.de>,
Ingo Molnar <mingo@...hat.com>
Subject: Re: [PATCH 1/2] x86: give names to realmode wakeup flags
On Tue, Jul 05, 2011 at 03:39:54PM -0700, H. Peter Anvin wrote:
> On 07/04/2011 03:35 PM, Kees Cook wrote:
> > Instead of using literals, use a common set of names for the
> > user-controlled realmode wakeup flags.
> >
> > Signed-off-by: Kees Cook <kees.cook@...onical.com>
>
> I'm sorry, but I really have to complain about this:
>
> This was a very unfriendly thing to do.
Obviously I wasn't trying to be unfriendly. :P
> You took a patch that is a bug fix to be considered for -stable,
> and you applied it *on top of a cleanup patch*.
It wasn't clear to me if the MISC_ENABLE reload should be considered for
stable (it does technically "more" than my original patch, and changes
the resume header structure, etc). If it should be forwarded to -stable,
that's fine too. I just didn't want to presume.
> They should not have been part of the same patchset,
> but *certainly* not in that order.
Since they hit the same .h file in the same location, I wasn't sure what
order to do it in. It seemed unhelpful to send them separately.
> Please resubmit.
Sure thing -- in the opposite order, or totally separate from each other?
-Kees
--
Kees Cook
Ubuntu Security Team
--
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/
Powered by blists - more mailing lists