From: Ray Kinsella <mdr@ashroe.eu>
To: Stephen Hemminger <stephen@networkplumber.org>
Cc: Stephen Coleman <omegacoleman@gmail.com>,
dev@dpdk.org, Ferruh Yigit <ferruh.yigit@xilinx.com>
Subject: Re: kni: check abi version between kmod and lib
Date: Thu, 21 Apr 2022 11:40:00 -0400 [thread overview]
Message-ID: <87czhao373.fsf@mdr78.vserver.site> (raw)
In-Reply-To: <20220421075444.6f872836@hermes.local>
Stephen Hemminger <stephen@networkplumber.org> writes:
> On Thu, 21 Apr 2022 12:38:26 +0800
> Stephen Coleman <omegacoleman@gmail.com> wrote:
>
>> KNI ioctl functions copy data from userspace lib, and this interface
>> of kmod is not compatible indeed. If the user use incompatible rte_kni.ko
>> bad things happen: sometimes various fields contain garbage value,
>> sometimes it cause a kmod soft lockup.
>>
>> Some common distros ship their own rte_kni.ko, so this is likely to
>> happen.
>>
>> This patch add abi version checking between userland lib and kmod so
>> that:
>>
>> * if kmod ioctl got a wrong abi magic, it refuse to go on
>> * if userland lib, probed a wrong abi version via newly added ioctl, it
>> also refuse to go on
>>
>> Bugzilla ID: 998
>
>
> Kernel API's are supposed to be 99% stable.
> If this driver was playing by the upstream kernel rules this would not
> have happened.
Well look, it is out-of-tree and never likely to be in-tree, so those
rules don't apply. Making sure the ABI doesn't change during the ABI
stablity period, should be good enough?
--
Regards, Ray K
next prev parent reply other threads:[~2022-04-21 15:40 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-21 4:38 kni: check abi version between kmod and lib Stephen Coleman
2022-04-21 14:16 ` Ray Kinsella
2022-04-21 14:54 ` Stephen Hemminger
2022-04-21 15:40 ` Ray Kinsella [this message]
2022-04-21 15:50 ` Stephen Hemminger
2022-04-22 8:46 ` Ray Kinsella
2022-04-22 10:07 ` Stephen Coleman
2022-04-21 16:34 ` [PATCH v2] " youcai
2022-04-24 8:51 ` [PATCH v3] " youcai
2022-04-24 10:35 ` Stephen Coleman
2023-07-04 2:56 ` Stephen Hemminger
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=87czhao373.fsf@mdr78.vserver.site \
--to=mdr@ashroe.eu \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@xilinx.com \
--cc=omegacoleman@gmail.com \
--cc=stephen@networkplumber.org \
/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.