On Wed, Feb 15, 2023 at 7:48 AM Stuart Henderson
wrote:
> Noticed while testing with LLVM 15, but it affects plain -current
> as well. If I take a binary that was linked with ld.bfd and strip it
> (i.e. this is now using llvm-strip), it breaks the output file in
> such a way that it cannot be
On Mon, Jan 30, 2023 at 05:03:30PM +0300, Vitaliy Makkoveev wrote:
> It makes sense to push solock() down to sosetopt() too. For a half cases
> (*pr_ctloutput)() is just null op, so there is no reason to call it.
> Also, a lot of things could be done without solock() held.
You do a bunch of
On Wed, Feb 15, 2023 at 12:02:46PM +0100, Tobias Heider wrote:
> Many of our networking daemons use proc.c to set up processes and ipc. I
> couldn't
> find two that are actually exactly the same, but it looks like none of them
> are ever
> using proc_ispeer, so here is a diff to delete it from
On Wed, Feb 15, 2023 at 12:02:46PM +0100, Tobias Heider wrote:
> Many of our networking daemons use proc.c to set up processes and ipc. I
> couldn't
> find two that are actually exactly the same, but it looks like none of them
> are ever
> using proc_ispeer, so here is a diff to delete it from
On Wed, 15 Feb 2023 09:03:55 -0700, "Todd C. Miller" wrote:
> It should not be removing .shstrtab. What happens if you tell
> llvm-strip to preserve .shstrtab? E.g. --keep-section .shstrtab?
Nevermind, I misread the readelf output, the stripped binary does
actually have .shstrtab.
- todd
It should not be removing .shstrtab. What happens if you tell
llvm-strip to preserve .shstrtab? E.g. --keep-section .shstrtab?
- todd
On Tue, 14 Feb 2023 17:47:00 -0800, Andrew Hewus Fresh wrote:
> With the perl update, we get a new version of unicode available to
> update this file as well. This was just running the script with the new
> perl version.
OK millert@
- todd
Noticed while testing with LLVM 15, but it affects plain -current
as well. If I take a binary that was linked with ld.bfd and strip it
(i.e. this is now using llvm-strip), it breaks the output file in
such a way that it cannot be executed:
: i386.p; cat a.c
#include
int main() {
15.02.2023 07:03, Florian Obser пишет:
> Oopsie.
>
> OK florian
Go ahead, OK kn
The following diff should allow most of utrace to run without kernel lock.
It makes utrace() less expensive if ktrace is not used.
--
:wq Claudio
Index: kern/kern_ktrace.c
===
RCS file: /cvs/src/sys/kern/kern_ktrace.c,v
retrieving
Thanks, but I'm not a developer, so I can't commit this.
Many of our networking daemons use proc.c to set up processes and ipc. I
couldn't
find two that are actually exactly the same, but it looks like none of them are
ever
using proc_ispeer, so here is a diff to delete it from all of them.
Index: sbin/iked/proc.c
12 matches
Mail list logo
