linux-kernel - Re: [PATCH] kbuild: scripts/gdb: bring the "abspath" back

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]

Date: Wed, 26 Jun 2024 00:08:15 +0900
From: Masahiro Yamada <masahiroy@...nel.org>
To: Joel Granados <j.granados@...sung.com>
Cc: Doug Anderson <dianders@...omium.org>, Jan Kiszka <jan.kiszka@...mens.com>, 
	Kieran Bingham <kbingham@...nel.org>, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] kbuild: scripts/gdb: bring the "abspath" back

On Mon, Jun 24, 2024 at 3:20 PM Joel Granados <j.granados@...sung.com> wrote:
>
> On Thu, Jun 20, 2024 at 02:51:41PM -0700, Doug Anderson wrote:
> > Hi,
> >
> > On Thu, Jun 20, 2024 at 12:48 PM Joel Granados via B4 Relay
> > <devnull+j.granados.samsung.com@...nel.org> wrote:
> > >
> > > From: Joel Granados <j.granados@...sung.com>
> > >
> > > Use the "abspath" call when symlinking the gdb python scripts in
> > > scripts/gdb/linux. This call is needed to avoid broken links when
> > > running the scripts_gdb target on a different build directory
> > > (O=builddir).

For preciseness, please rephrase it to something like this:

 running the scripts_gdb target on a build directory located
 directly under the source tree (e.g., O=builddir).






O=foo/builddir does not cause this issue because
$(src) is already an absolute path.

This issue occurs only when the output directory is
a direct subdirectory of the source tree, in other words,
srctree is '..'


See this line:

https://github.com/torvalds/linux/blob/v6.10-rc5/Makefile#L254







-- 
Best Regards
Masahiro Yamada