linux-kernel - Re: [patch] suspend/resume self-test

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]

Message-ID: <20080218130914.GC17697@elte.hu>
Date:	Mon, 18 Feb 2008 14:09:14 +0100
From:	Ingo Molnar <mingo@...e.hu>
To:	David Brownell <david-b@...bell.net>
Cc:	Pavel Machek <pavel@....cz>, rjw@...k.pl,
	linux-pm@...ts.linux-foundation.org, linux-kernel@...r.kernel.org,
	Linus Torvalds <torvalds@...ux-foundation.org>
Subject: Re: [patch] suspend/resume self-test


* David Brownell <david-b@...bell.net> wrote:

> > >   - Includes a command line parameter, which needs work yet ... it
> > >     currently turns this test off, but it should also let the target
> > >     state be specified (and maybe even default to "no test").
> 
> I think "no test" should be the default; STR working sanely on x86 is 
> unfortunately too much a surprise.  Someone more active in PM testing 
> should update that.

All i'm asking for is to make the self-test easily accessible. Not for 
it to blow up in the face of users who do not ask for it.

And, at least to me, there seems to be a rather apparent correlation 
between "suspend/resume regressions caught as early as possible" and the 
future, desired state of: "STR working sanely on x86" ;-)

You really seem to treat S2R suckiness as a fact of life, but it isnt. 
Yes, it's a hard field for a number of reasons, but we could be doing _a 
lot_ better. One of them would be this "notice s2r breakage when i 
create or add the patch that breaks it" angle.

        Ingo

--
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/