linux-kernel - Re: Inline hunt results for 4.3.0-rc1

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: <562F98CE.4070200@hurleysoftware.com>
Date:	Tue, 27 Oct 2015 11:31:26 -0400
From:	Peter Hurley <peter@...leysoftware.com>
To:	Denys Vlasenko <vda.linux@...glemail.com>
Cc:	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	Oleg Nesterov <oleg@...hat.com>,
	Greg KH <gregkh@...uxfoundation.org>
Subject: Re: Inline hunt results for 4.3.0-rc1

[ +cc Greg KH]

On 10/27/2015 10:32 AM, Denys Vlasenko wrote:
> Hi,
> 
> I have created a set of semi-automated scripts which look for
> large inlines in the kernel.
> 
> Recently I taught it to even generate "git format-patch" patches
> (unfortunately, only for inlines in *.c files, not *.h),
> and here are they for 4.3.0-rc1 - i.e. current Linus tree.
> 
> Submitting 300+ patches separately would amount to spamming,
> instead I encourage people to take a look at the patches
> on the Web:
> 
>     http://busybox.net/~vda/inline_hunt/4.3.0-rc1/

Looking over the drivers/tty/* patches, all of the patches
that save 300+ and 1000+ look ok to me, so if you want to
send those as a series (to the tty maintainers), I'll be
happy to mark them reviewed.

Wrt the "saves 100+' patches, some are ok, some are not,
and some I'd like to eliminate in a different way.
If you want to send those as a separate series, I could
mark as reviewed the ok patches, indicate which ones
to drop and which patches I'd be willing to rework.

Regards,
Peter Hurley


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