From mboxrd@z Thu Jan 1 00:00:00 1970 From: Michael Tremer To: development@lists.ipfire.org Subject: Re: [PATCH] Kernel: Block non-UID-0 profiling completely Date: Fri, 04 Feb 2022 16:56:41 +0000 Message-ID: <4E7F76F6-ED52-4C00-AF0D-76359C80042E@ipfire.org> In-Reply-To: <95330529-1dc6-9cec-5e94-555cd8b2ccae@ipfire.org> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============2043208555655266105==" List-Id: --===============2043208555655266105== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Hello, > On 4 Feb 2022, at 13:45, Peter M=C3=BCller wro= te: >=20 > Hello Michael, >=20 > [...] >=20 >>>> #lib/modules/KVER-ipfire/build/include/linux/perf_event.h >>>> +#lib/modules/KVER-ipfire/build/include/linux/perf_event.h.orig >>>=20 >>> We should not install any files like this. >>=20 >> Hm. I wonder where it came from. Perhaps I forgot a "./make.sh clean" afte= r the first attempt. >>=20 >> Will check and report back. >=20 > after running a clean build, this file stays present. It's attached to this= mail. >=20 > It is odd to see this happening, as the additional "patch" command introduc= ed by this > patch does not differ from those already present in the kernel's LFS file, = except for > the patch file itself. If the patch doesn=E2=80=99t match exactly, patch will create backup files so= that you can fix anything manually if things broke. What you can do is either to rediff the patch that it applies cleanly, or you= can use this option: --no-backup-if-mismatch Do not back up a file if the patch does not match the file exactly and if backups are not otherwise requested. This is the default if patch is conforming to POSIX. This should however be the default. -Michael >=20 > Can you give me any hint on where to look next? >=20 > Thanks, and best regards, > Peter M=C3=BCller --===============2043208555655266105==--