linux-kernel - Re: [PROBLEM] hard-lock with kmemtrace, relayfs, and splice

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]

Date:	Tue, 14 Oct 2008 08:13:55 +0300
From:	Pekka Enberg <penberg@...helsinki.fi>
To:	Tom Zanussi <zanussi@...cast.net>
CC:	Eduard - Gabriel Munteanu <eduard.munteanu@...ux360.ro>,
	jens.axboe@...cle.com, linux-kernel@...r.kernel.org
Subject: Re: [PROBLEM] hard-lock with kmemtrace, relayfs, and splice

Hi Tom,

Tom Zanussi wrote:
> To me, that sounds like how it should work - if kmemtrace is disabled,
> it shouldn't be logging anything, and that's in fact what I saw when
> debugging this - it started out disabled and therefore nothing being
> logged to relay (printks confirmed that).  When I wrote 1 to the enabled
> file, data started getting logged to relay and to the *.out files.
> 
> So I don't know why the enabled state behaves the way it does, or if
> it's unexpected, but that anyway doesn't seem like a relay problem to
> me.

Oh, right. Looking at kmemtraced.c, we never enable kmemtrace, just 
disable it (which doesn't make much sense). Bug in README or the code. 
Eduard?

Btw, Tom, you can add my

Tested-by: Pekka Enberg <penberg@...helsinki.fi>

to your patch if you want. Are you going to send it to Andrew or do you 
want me to pick it up with rest of the kmemtrace patches?

		Pekka
--
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/