linux-kernel - Re: 2.6.23-rc3-mm1: cannot stat `vdso.so.dbg'

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:	Wed, 22 Aug 2007 17:32:32 -0700 (PDT)
From:	Roland McGrath <roland@...hat.com>
To:	Andi Kleen <ak@...e.de>
Cc:	Andrew Morton <akpm@...ux-foundation.org>,
	Alexey Dobriyan <adobriyan@...ru>, linux-kernel@...r.kernel.org
Subject: Re: 2.6.23-rc3-mm1: cannot stat `vdso.so.dbg'

> The problem is they're two patching consecutively patching the same
> file with 100% identical subject/description.
> 
> So either: they should be merged together into one patch
> or the second (or first) needs a new description/subject

They do the same thing for the x86_64 ia32-compat and x86_64 native vDSOs,
respectively. 

Subject: [PATCH 1/2] x86_64 ia32 vDSO: install unstripped copies on disk
Subject: [PATCH 2/2] x86_64 vDSO: install unstripped copies on disk

Andrew called them

x86_64-ia32-vdso-install-unstripped-copies-on-disk
x86_64-vdso-install-unstripped-copies-on-disk

The names/subjects are not identical, but differ in having "ia32" or not.
That is really the only difference between the two patches, too.

> TBD this needs a proper changelog/subject from Roland. I have no idea what 
> it does

I don't now what is unclear about the log entry.  Yes, each log entry says
the same thing after the first (Subject) line.  Each one relates to a
different arch/x86_64/subdirectory/Makefile that creates vDSO images.
Prepend "This applies to the x86_64/vdso native vDSO building." or
"This applies to the x86_64/ia32 vDSO building." to the log if you prefer.

Thanks,
Roland
-
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/