linux-kernel - [GIT] /proc update

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-next>] [day] [month] [year] [list]

Message-ID: <20081023183649.GA13432@x200.localdomain>
Date:	Thu, 23 Oct 2008 22:36:49 +0400
From:	Alexey Dobriyan <adobriyan@...il.com>
To:	torvalds@...l.org
Cc:	linux-kernel@...r.kernel.org
Subject: [GIT] /proc update

Linus, please, pull from

	git://git.kernel.org/pub/scm/linux/kernel/git/adobriyan/proc.git proc

to get
a) /proc/*/smaps fix aka "[vsyscall] is listed twice"
b) proc_misc.c disintegration patches which spread that collective
   dumping ground into sensible pieces,
c) trivial things.

Regarding (b), it wasn't in -next because of huge rejects, it wasn't in
-mm because of huge rejects, but (!) various people acked pieces, it was
booted in several configurations here and proc files were created and
worked as usual, it's trivial.

Also, looks like, I can't put it into -next or into -mm and keep it for
several months there because of rejects, and keeping it out of system
will buy me approximately the same amount of testing as there is now.

However, fs/proc/ compiliation was tested on huge cross-compile setup here
and many, many randconfigs without warnings or errors.

Now, if you don't buy it, pull from

	git://git.kernel.org/pub/scm/linux/kernel/git/adobriyan/proc.git proc-conservative

to get just /proc/*/smaps fix and trivial things.
--
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/