>> @@ -708,11 +708,11 @@ static void svc_addr(struct seq_file *seq, struct sockaddr_atmsvc *addr)
>> static int e164[] = { 1, 8, 4, 6, 1, 0 };
>>
>> if (*addr->sas_addr.pub) {
>> - seq_printf(seq, "%s", addr->sas_addr.pub);
>> + seq_puts(seq, addr->sas_addr.pub);
>
> Which opens a lot of security concerns.
How? - The passed string is just copied into a buffer finally, isn't it?
> Never do this again.
Why do you not like such a small source code transformation at the moment?
> P.S. I'm wondering what would be first,
I am curious on how communication difficulties can be adjusted.
> Markus starts looking into the actual code,
I inspected the original source code to some degree.
https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/tree/fs/seq_file.c?id=895c0dde398510a5b5ded60e5064c11b94bd30ca#n682
https://elixir.free-electrons.com/linux/v4.15-rc6/source/fs/seq_file.c#L660
> or most (all) of the maintainers just ban him.
The change acceptance is varying for various reasons by the involved contributors.
Regards,
Markus
--
To unsubscribe from this list: send the line "unsubscribe kernel-janitors" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
