linux-kernel - Re: rfc: trivial patches and slow deaths?

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: <1377038985.2016.96.camel@joe-AO722>
Date:	Tue, 20 Aug 2013 15:49:45 -0700
From:	Joe Perches <joe@...ches.com>
To:	Andrew Morton <akpm@...ux-foundation.org>
Cc:	Rob Landley <rob@...dley.net>, Jiri Kosina <jkosina@...e.cz>,
	LKML <linux-kernel@...r.kernel.org>,
	kernel-janitors <kernel-janitors@...r.kernel.org>
Subject: Re: rfc: trivial patches and slow deaths?

On Tue, 2013-08-20 at 15:24 -0700, Andrew Morton wrote:
> On Tue, 20 Aug 2013 15:11:18 -0700 Joe Perches <joe@...ches.com> wrote:
> 
> > Andrew?  Do you want to handle patches for defects that
> > are both obvious _and_ trivial?
> 
> I look at everything!

Well, I guess I'll have to start cc'ing you on
the trivial in case the eyestrain gets to you.

[]

> I somewhat disagree that even
> https://patchwork.kernel.org/patch/2833648/ was trivial.  It changes
> the format of kernel logs and might have implications for people who
> are parsing those logs.

I think there are _very_ few instances where dmesg
output should be kept constant for scrapers.

The format of an oops is about the only one I can
think of where it's reasonable to do so.

> one needs to read each and every
> conversion and decide on the risk factor.

Enjoy...

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