linux-kernel - Re: [PATCH] cifs: Do not enable debugging code by default

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: <CAH2r5mt622hpU=iC8BL1gvSD-fnjWnE=Qm+pph_AY5ob0zbejQ@mail.gmail.com>
Date:	Tue, 18 Dec 2012 09:33:15 -0600
From:	Steve French <smfrench@...il.com>
To:	Borislav Petkov <bp@...en8.de>, Jeff Layton <jlayton@...hat.com>,
	Steve French <smfrench@...il.com>,
	LKML <linux-kernel@...r.kernel.org>,
	Joe Perches <joe@...ches.com>,
	Steve French <sfrench@...ba.org>, linux-cifs@...r.kernel.org
Subject: Re: [PATCH] cifs: Do not enable debugging code by default

On Tue, Dec 18, 2012 at 9:19 AM, Borislav Petkov <bp@...en8.de> wrote:
> On Tue, Dec 18, 2012 at 10:07:02AM -0500, Jeff Layton wrote:
>> Yeah, not many do, but presumably they'll set it once and forget about
>> it. Once someone straightens them out, they should rarely break.
>>
>> OTOH, the value of defaulting to "N" is pretty low here. Maybe it
>> would just be best to just drop this patch and have the embedded folks
>> turn this off on their own.
>
> Yeah, sure.

I am ok with disabling it for embedded, but probably easier to drop
it.   The real benefit will come when someone familiar with dynamic
trace points comes up with some good examples for file system(s) and
the VFS so we can reduce our dependency on static tracing.



-- 
Thanks,

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