Date: Wed, 25 Aug 2021 15:19:12 -0600 From: Alan Somers <asomers@freebsd.org> To: FreeBSD CURRENT <freebsd-current@freebsd.org> Subject: ses ioctl API/ABI stability Message-ID: <CAOtMX2g%2B6Zp_TxKjFhgE3DhHQhUyAvNsUCO2d-1tuz-o9e=FPg@mail.gmail.com>
next in thread | raw e-mail | index | archive | help
We usually try to maintain backwards compatibility forever. But is that necessary for the ses(4) ioctls? There are several problems with them as currently defined. They lack type safety, lack automatic copyin/copyout handling, and one of them can overrun a user buffer. I would like to fix them, but adding backwards-compatibility versions would almost negate the benefit. Or, can we consider this to be an internal API, changeable at will, as long as sesutil's CLI remains the same? -Alan
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAOtMX2g%2B6Zp_TxKjFhgE3DhHQhUyAvNsUCO2d-1tuz-o9e=FPg>