linux-kernel - Re: Wiring up direct socket calls on x86

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <87oajwrilb.fsf@igel.home>
Date:	Tue, 30 Jun 2015 23:29:04 +0200
From:	Andreas Schwab <schwab@...ux-m68k.org>
To:	Andy Lutomirski <luto@...capital.net>
Cc:	X86 ML <x86@...nel.org>,
	"linux-kernel\@vger.kernel.org" <linux-kernel@...r.kernel.org>,
	Alexander Larsson <alexl@...hat.com>,
	Cosimo Cecchi <cosimo@...lessm.com>,
	Dan Nicholson <nicholson@...lessm.com>,
	Network Development <netdev@...r.kernel.org>,
	libc-alpha <libc-alpha@...rceware.org>
Subject: Re: Wiring up direct socket calls on x86_32 Linux?

Andy Lutomirski <luto@...capital.net> writes:

> Glibc people: If Linux wired up the syscalls, would glibc use them?

Not automatically.  It needs to be compatible with the configured
minimum kernel version, so runtime probing would needed to be
implemented.

Andreas.

-- 
Andreas Schwab, schwab@...ux-m68k.org
GPG Key fingerprint = 58CA 54C7 6D53 942B 1756  01D3 44D5 214B 8276 4ED5
"And now for something completely different."
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/