[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20100630101329.6bc57392@lxorguk.ukuu.org.uk>
Date: Wed, 30 Jun 2010 10:13:29 +0100
From: Alan Cox <alan@...rguk.ukuu.org.uk>
To: Kees Cook <kees.cook@...onical.com>
Cc: linux-kernel@...r.kernel.org, Greg Kroah-Hartman <gregkh@...e.de>,
Andrew Morton <akpm@...ux-foundation.org>,
Tejun Heo <tj@...nel.org>,
Veaceslav Falico <vfalico@...hat.com>,
Alexander Viro <viro@...iv.linux.org.uk>,
Oleg Nesterov <oleg@...hat.com>,
KOSAKI Motohiro <kosaki.motohiro@...fujitsu.com>,
Neil Horman <nhorman@...driver.com>,
Roland McGrath <roland@...hat.com>,
Ingo Molnar <mingo@...e.hu>,
Peter Zijlstra <a.p.zijlstra@...llo.nl>,
Hidetoshi Seto <seto.hidetoshi@...fujitsu.com>,
Stefani Seibold <stefani@...bold.net>,
Thomas Gleixner <tglx@...utronix.de>,
Eric Paris <eparis@...hat.com>,
James Morris <jmorris@...ei.org>,
"Andrew G. Morgan" <morgan@...nel.org>,
Dhaval Giani <dhaval.giani@...il.com>,
"Serge E. Hallyn" <serue@...ibm.com>,
Steve Grubb <sgrubb@...hat.com>,
Christoph Hellwig <hch@....de>, linux-fsdevel@...r.kernel.org
Subject: Re: [PATCH v2] sanitize task->comm to avoid leaking escape codes
> What I do have interest in is fixing get_task_comm's use of buffers, which
> is theoretically problematic in some future where someone accidentally
> calls it with a buffer smaller than sizeof(task->comm).
Lots of things are theoretically problematic and kernel would take a week
to boot if we covered them all 8)
Having a
struct task_name {
char [propersize];
}
would produce the same code as far as I can tell and so typechecking
though - so as you say it can be done sanely.
Alan
--
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