From: Petr Vorel <pvorel@suse.cz>
To: ltp@lists.linux.it
Subject: [LTP] [PATCH v4 1/2] pty04: Use guarded buffers for transmission
Date: Wed, 6 May 2020 14:17:04 +0200 [thread overview]
Message-ID: <20200506121704.GA8586@dell5510> (raw)
In-Reply-To: <1139985312.11485617.1588766778300.JavaMail.zimbra@redhat.com>
Hi Jan,
> > > -#if defined(HAVE_LINUX_IF_PACKET_H) && defined(HAVE_LINUX_IF_ETHER_H)
> > > +#include <linux/version.h>
> > Shouldn't we also check for <linux/version.h> with autotools? Or are kernel
> > headers mandatory for LTP build?
> We already include this header in some syscalls tests, so I assumed it won't be an issue.
OK, no problem.
> > > +
> > > +#if defined(HAVE_LINUX_IF_PACKET_H) && defined(HAVE_LINUX_IF_ETHER_H) \
> > > + && LINUX_VERSION_CODE >= KERNEL_VERSION(4, 10, 0)
> > > #include <linux/if_packet.h>
> > > #include <linux/if_ether.h>
> > > @@ -373,6 +376,6 @@ static struct tst_test test = {
> > > #else
> > > -TST_TEST_TCONF("Need <linux/if_packet.h> and <linux/if_ether.h>");
> > > +TST_TEST_TCONF("Need <linux/if_packet.h> and <linux/if_ether.h> and
> > > 4.10+");
> > +1.
> > BTW, why this tests requires 4.10 for runtime?
> It's for compilation. struct can_frame fields it's using were introduced in 4.10.
Do you mean a2f11835994e ("can.h: make padding given by gcc explicit") from
v4.2-rc1? + there is no change for include/uapi/linux/can.h in 4.10.
This is just a separate question to this fix (thank you for finding a solution).
Kind regards,
Petr
next prev parent reply other threads:[~2020-05-06 12:17 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
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 [this message]
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=20200506121704.GA8586@dell5510 \
--to=pvorel@suse.cz \
--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