some syscalls have arguments that are read/write. for example, getsockopt
passes in a pointer to a length that has to be set correctly first, and then
the kernel will adjust it when returning. being able to see both values is
important when getting an error so you can see what the user sent up
On Wed, Aug 19, 2015 at 04:59:38PM -0400, Mike Frysinger wrote:
On 19 Aug 2015 22:36, Dmitry V. Levin wrote:
On Wed, Aug 19, 2015 at 03:17:39PM -0400, Mike Frysinger wrote:
some syscalls have arguments that are read/write. for example,
getsockopt
passes in a pointer to a length that
On 19 Aug 2015 22:36, Dmitry V. Levin wrote:
On Wed, Aug 19, 2015 at 03:17:39PM -0400, Mike Frysinger wrote:
some syscalls have arguments that are read/write. for example, getsockopt
passes in a pointer to a length that has to be set correctly first, and then
the kernel will adjust it
