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]

Message-Id: <20081106153555.ed45a874.sfr@canb.auug.org.au>
Date:	Thu, 6 Nov 2008 15:35:55 +1100
From:	Stephen Rothwell <sfr@...b.auug.org.au>
To:	David Miller <davem@...emloft.net>
Cc:	alan@...rguk.ukuu.org.uk, linux-kernel@...r.kernel.org,
	wli@...omorphy.com, sparclinux@...r.kernel.org
Subject: Re: tty warning

Hi Dave,

On Wed, 05 Nov 2008 20:25:57 -0800 (PST) David Miller <davem@...emloft.net> wrote:
>
> 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 :)

Yeah, I guess that is when the compilers started complaining.

Oh, well :-(

[BTW, the number of warnings is itself becoming a real problem ... :-( ]
-- 
Cheers,
Stephen Rothwell                    sfr@...b.auug.org.au
http://www.canb.auug.org.au/~sfr/

Content of type "application/pgp-signature" skipped