linux-kernel - Re: [RFC] kconfig/mconf.c: revision of curses initialization.

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: <20120830125912.GA14031@sepie.suse.cz>
Date:	Thu, 30 Aug 2012 14:59:12 +0200
From:	Michal Marek <mmarek@...e.cz>
To:	Dirk Gouders <gouders@...bocholt.fh-gelsenkirchen.de>
Cc:	Arnaud Lacombe <lacombar@...il.com>, linux-kernel@...r.kernel.org,
	linux-kbuild@...r.kernel.org
Subject: Re: [RFC] kconfig/mconf.c: revision of curses initialization.

On Mon, Aug 06, 2012 at 05:19:43PM +0200, Dirk Gouders wrote:
> Hello,
> 
> I noticed that in mconf, initscr() is called twice -- as far as I found
> out since commit d0e1e09568.
> 
> In case you see a need to fix that:
> 
> I first thought about simply removing the call in init_dialog() in
> util.c but then had the feeling that saving of initial cursor positions
> also perhaps is better done in that function...
> 
> Dirk
> 
> ------------------------------------------------------------------------
> From 1a4022eedbee6032dea16f67bbe4028a8d3d07a0 Mon Sep 17 00:00:00 2001
> From: Dirk Gouders <gouders@...bocholt.fh-gelsenkirchen.de>
> Date: Mon, 6 Aug 2012 16:48:23 +0200
> Subject: [PATCH] kconfig/mconf.c: revision of curses initialization.
> 
> Since commit d0e1e09568 initscr() is called twice in mconf.
> 
> Do it only in init_dialog() in util.c and there also save the
> cursor position for the signal handler in mconf.c.
> 
> Signed-off-by: Dirk Gouders <gouders@...bocholt.fh-gelsenkirchen.de>

Applied to kbuild.git#kconfig, thanks.

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