| 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
| ||
|
Date: Mon, 15 Mar 2010 13:03:11 -0400 From: Mathieu Desnoyers <mathieu.desnoyers@...icios.com> To: ltt-dev@...ts.casi.polymtl.ca, linux-kernel@...r.kernel.org Cc: Changli Gao <xiaosuo@...il.com>, Jens Axboe <jens.axboe@...cle.com> Subject: [RELEASE] LTTng 0.199 for Linux 2.6.33 Hi everyone, I just released an updated LTTng tree/tarball that is now based on the 2.6.33 kernel. As always, comments and testing results are welcome. Website: http://lttng.org Kernel tree: http://git.kernel.org/?p=linux/kernel/git/compudj/linux-2.6-lttng.git git://git.kernel.org/pub/scm/linux/kernel/git/compudj/linux-2.6-lttng.git Tarballs: http://lttng.org/files/lttng/patch-2.6.33-lttng-0.199.tar.bz2 There has been some changes in the way splice() works between 2.6.32 and 2.6.33 (commit cc56f7de7f00d188c7c4da1e9861581853b9e92f). It now checks for NULL llseek fop in addition to check for the no_llseek. In LTTng, we use the offset value directly in our own implementation of the splice_read fop, so there is no point in having a llseek fop. The solution I used to bypass this check is to create my own copy of "no_llseek" in ltt-relay-splice.c, which does basically nothing, but makes do_splice() happy. Thanks, Mathieu -- Mathieu Desnoyers Operating System Efficiency Consultant EfficiOS Inc. http://www.efficios.com -- 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/
Powered by blists - more mailing lists