linux-hardening - Re: [PATCH v3][next] tty: tty_buffer: Avoid hundreds of -Wflex-array-member-not-at-end warnings

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 for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <7c396d56-a2ea-4cb5-8a10-a2b78cebfaeb@embeddedor.com>
Date: Fri, 7 Feb 2025 09:53:30 +1030
From: "Gustavo A. R. Silva" <gustavo@...eddedor.com>
To: Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
 "Gustavo A. R. Silva" <gustavoars@...nel.org>
Cc: Jiri Slaby <jirislaby@...nel.org>, linux-kernel@...r.kernel.org,
 linux-serial@...r.kernel.org, linux-hardening@...r.kernel.org
Subject: Re: [PATCH v3][next] tty: tty_buffer: Avoid hundreds of
 -Wflex-array-member-not-at-end warnings


>>   	unsigned int used;
>>   	unsigned int size;
>>   	unsigned int commit;
>> -	unsigned int lookahead;		/* Lazy update on recv, can become less than "read" */
>> +	unsigned int lookahead; /* Lazy update on recv, can become less than "read" */
> 
> Coding style change?

(Whaa? for some reason your response didn't reach my inbox until today)

It seems I got a bit too proactive.

What do you think about the rest of the patch?

Thanks!
-Gustavo