From: Stephen Hemminger <stephen@networkplumber.org>
To: Markus Theil <markus.theil@tu-ilmenau.de>
Cc: ferruh.yigit@intel.com, dev@dpdk.org, markus.theil@secunet.com,
Michael Pfeiffer <michael.pfeiffer@tu-ilmenau.de>
Subject: Re: [PATCH v2] kni: fix ioctl signature
Date: Sun, 28 Nov 2021 15:05:31 -0800 [thread overview]
Message-ID: <20211128150531.0a9dc798@hermes.local> (raw)
In-Reply-To: <20211128131426.68238-1-markus.theil@tu-ilmenau.de>
On Sun, 28 Nov 2021 14:14:26 +0100
Markus Theil <markus.theil@tu-ilmenau.de> wrote:
> From: Markus Theil <markus.theil@secunet.com>
>
> Fix kni's ioctl signature to correctly match the kernel's
> structs. This shaves off the (void*) casts and uses struct file*
> instead of struct inode*. With the correct signature, control flow
> integrity checkers are no longer confused at this point.
>
> Signed-off-by: Markus Theil <markus.theil@secunet.com>
> Tested-by: Michael Pfeiffer <michael.pfeiffer@tu-ilmenau.de>
> ---
> v2: adapt to suggestions from Ferruh Yigit
>
> kernel/linux/kni/kni_misc.c | 14 +++++++-------
> 1 file changed, 7 insertions(+), 7 deletions(-)
> -static int
> -kni_compat_ioctl(struct inode *inode, uint32_t ioctl_num,
> +static long
> +kni_compat_ioctl(struct file *file, uint32_t ioctl_num,
> unsigned long ioctl_param)
> {
Shouldn't be uint32_t should be unsigned int.
In fs.h.
long (*compat_ioctl) (struct file *, unsigned int, unsigned long);
next prev parent reply other threads:[~2021-11-28 23:05 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-20 13:14 [PATCH] kni: fix ioctl signature Markus Theil
2021-11-22 13:19 ` Ferruh Yigit
2021-11-28 13:14 ` [PATCH v2] " Markus Theil
2021-11-28 23:05 ` Stephen Hemminger [this message]
2021-12-03 7:19 ` [PATCH v3] " Markus Theil
2021-12-03 16:28 ` Stephen Hemminger
2022-02-02 19:59 ` Thomas Monjalon
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=20211128150531.0a9dc798@hermes.local \
--to=stephen@networkplumber.org \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@intel.com \
--cc=markus.theil@secunet.com \
--cc=markus.theil@tu-ilmenau.de \
--cc=michael.pfeiffer@tu-ilmenau.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.