linux-kernel - Re: tty warning

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, 05 Nov 2008 20:25:57 -0800 (PST)
From:	David Miller <davem@...emloft.net>
To:	sfr@...b.auug.org.au
Cc:	alan@...rguk.ukuu.org.uk, linux-kernel@...r.kernel.org,
	wli@...omorphy.com, sparclinux@...r.kernel.org
Subject: Re: tty warning

From: Stephen Rothwell <sfr@...b.auug.org.au>
Date: Thu, 6 Nov 2008 15:24:21 +1100

> These are things like:
> 
>                 termios->c_cc[VTIME] = 0;
> 
> termios is a (struct ktermios *) which has "cc_t c_cc[NCCS];".  NCCS is
> 17 and VTIME is also 17.  I assume the intention is to actually fill in
> _x_cc[0], but why is it done this way and not more directly?

It's just some historical stuff.

I've tried to rectify it, but it is non-trivial to fix and
all it does is pacify a warning rather than fix a real problem
so... ;-)

This has been brought up perhaps 5 or 6 times in the past half
year :)
--
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/