From: Richard Palethorpe <rpalethorpe@suse.de>
To: ltp@lists.linux.it
Subject: [LTP] [PATCH v4 2/2] pty04: Add SLCAN ldisc and check for CVE-2020-11494
Date: Tue, 05 May 2020 16:18:58 +0100 [thread overview]
Message-ID: <87a72ms93x.fsf@our.domain.is.not.set> (raw)
In-Reply-To: <20200505135531.GA30346@dell5510>
Hello,
Petr Vorel <pvorel@suse.cz> writes:
> Hi Cyril, Richard,
>
>> Hi!
>> Both pushed, thanks.
>
> This test does not compile on kernel older than v4.2-rc1 (2015),
> because __pad, __res0 and __res1 are missing. They were added in
> a2f11835994e ("can.h: make padding given by gcc explicit").
I suppose I can just drop the header and define it inline as we need the
fallback anyway.
>
> This got propagated on CentOS 6. I'd be for dropping it after release (most of
> the problems are due old gcc 4), but v4.1 is still too new, so I'll send some
> autotools based fix for this.
>
> Kind regards,
> Petr
--
Thank you,
Richard.
next prev parent reply other threads:[~2020-05-05 15:18 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-05 10:16 [LTP] [PATCH v4 1/2] pty04: Use guarded buffers for transmission Richard Palethorpe
2020-05-05 10:16 ` [LTP] [PATCH v4 2/2] pty04: Add SLCAN ldisc and check for CVE-2020-11494 Richard Palethorpe
2020-05-05 13:35 ` Cyril Hrubis
2020-05-05 13:55 ` Petr Vorel
2020-05-05 15:18 ` Richard Palethorpe [this message]
2020-05-05 15:27 ` Petr Vorel
2020-05-05 13:37 ` [LTP] [PATCH v4 1/2] pty04: Use guarded buffers for transmission Petr Vorel
2020-05-05 14:47 ` Richard Palethorpe
2020-05-05 15:01 ` Petr Vorel
2020-05-05 15:11 ` Petr Vorel
2020-05-06 8:47 ` Richard Palethorpe
2020-05-06 10:49 ` Jan Stancek
2020-05-06 10:56 ` Li Wang
2020-05-06 11:14 ` Jan Stancek
2020-05-06 11:38 ` Petr Vorel
2020-05-06 12:06 ` Jan Stancek
2020-05-06 12:17 ` Petr Vorel
2020-05-06 12:20 ` Jan Stancek
2020-05-06 12:49 ` Cyril Hrubis
2020-05-06 13:49 ` Petr Vorel
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87a72ms93x.fsf@our.domain.is.not.set \
--to=rpalethorpe@suse.de \
--cc=ltp@lists.linux.it \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox