[Pkg-privacy-maintainers] Bug#801224: torsocks: [syscall] Unsupported syscall number 250

[intrigeri]

Control: tag -1 + moreinfo

Hi Niels,

Niels Thykier wrote (07 Oct 2015 15:14:28 GMT) :
> Running polularity-contest with torsocks gives a warning:

> """
> torsocks /etc/cron.daily/popularity-contest --crond
> [Oct 07 17:11:53] WARNING torsocks[5038]: [syscall] Unsupported syscall number 250.
> Denying the call (in tsocks_syscall() at syscall.c:465)
> """

syscall numbers are architecture dependent, so: what architecture did
you experience this on?

E.g. 250 could be:

* keyctl on amd64:
  https://sources.debian.net/src/linux/3.16.7-ckt11-1+deb8u6~bpo70+1/arch/x86/syscalls/syscall_64.tbl/#L259
* fadvise64 on i386:
  https://sources.debian.net/src/linux/3.16.7-ckt11-1+deb8u6~bpo70+1/arch/x86/syscalls/syscall_32.tbl/#L259

Once I have this info I'll ping upstream about it, so the
corresponding syscall is allowed (if that's safe) in next release.

(I can't reproduce this here with torsocks 2.1.0-2 on sid.)

Cheers,
--
intrigeri