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] [day] [month] [year] [list]
Date:	Thu, 7 Mar 2013 09:32:02 +0000
From:	Russell King - ARM Linux <linux@....linux.org.uk>
To:	Kukjin Kim <kgene.kim@...sung.com>
Cc:	'Paul Bolle' <pebolle@...cali.nl>,
	'Ben Dooks' <ben-linux@...ff.org>,
	linux-arm-kernel@...ts.infradead.org,
	linux-samsung-soc@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] ARM: S3C24XX: drop "select MACH_N35"

On Thu, Mar 07, 2013 at 10:14:19AM +0900, Kukjin Kim wrote:
> Russell King - ARM Linux wrote:
> > And deleting entries from it is pointless if they've ever been in the
> > kernel.
> 
> OK, I see and agree.

The issue is that the database system "locks" an entry into the file as
soon as support is merged into mainline for the platform.  The reason
for this is that as soon as the support gets merged into a kernel verison,
that symbol is then referenced.

If anyone goes to the website to download a new copy of the file, it then
must continue to contain that symbol because they may be using the file
with any kernel version - maybe a version of the kernel with your platform
support in - and maybe they're using something that references the
generated ID/macros from your entry.

Updates to the file in the mainline kernel are merely re-downloads of the
file from the website and committed.

So, deleting entries once used in mainline is extremely problematical.  If
someone commits such a patch, my next update from the website/database to
the file will put it back.  Hence the problem.
--
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

Powered by Openwall GNU/*/Linux Powered by OpenVZ