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: <20100614141447.d11c5dac.akpm@linux-foundation.org>
Date:	Mon, 14 Jun 2010 14:14:47 -0700
From:	Andrew Morton <akpm@...ux-foundation.org>
To:	TAMUKI Shoichi <tamuki@...et.gr.jp>
Cc:	Ingo Molnar <mingo@...e.hu>, Anton Blanchard <anton@...ba.org>,
	Andi Kleen <andi@...stfloor.org>,
	Andy Green <andy@...mcat.com>,
	Randy Dunlap <randy.dunlap@...cle.com>,
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH v2] panic: keep blinking in spite of long spin timer
 mode

On Fri, 11 Jun 2010 07:31:13 +0900
TAMUKI Shoichi <tamuki@...et.gr.jp> wrote:

> Hello,
> 
> On Wed, 9 Jun 2010 15:15:52 -0700 Andrew Morton wrote:
> 
> > Morse code?  Kidding?
> 
> I'm sorry, I'm confusing you.
> 
> > Sorry, no.  Nobody who uses this feature will know what what
> > "words per minute" means.  It's nutty!
> 
> That is just a strained interpretation where the measure of the
> blinking speed comes from.  The description of "words per minute"
> has already disappeared in the latest patch.
> 
> > Please remind me why we're making this configurable at all.  Can't we
> > just hardwire the thing to 1Hz or something?  Add an
> > im_using_a_hypervisor boot option or something, if necessary?
> 
> For now, gta02_panic_blink(), one of panic_blink() users, expects a
> 10Hz call rate.  IOW, it blinks at 5Hz (i.e. panicblink=36).  I think
> that the desirable blinking speed is different according to devices.
> 

gta02_panic_blink() simply toggles a gpio output.  It's trivial to
convert that function to implement whatever behaviour we decide upon. 
Err, in fact your patch already does that.

I still don't think we should have a kernel boot option for this - it
just doesn't seem useful enough.  Can we please just hard-wire the
blinking frequency?  And once we've done that, we don't have to jump
through hoops with this "wpm" thing.  We can use Hz.

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

Powered by Openwall GNU/*/Linux Powered by OpenVZ