ses ioctl API/ABI stability

From: Alan Somers <>
Date: Wed, 25 Aug 2021 15:19:12 -0600
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?
Received on Wed Aug 25 2021 - 21:19:12 UTC

Original text of this message