[Bug 246630] stable/11 regression: base.txz reproducibility depends on number of cpu cores

2020-06-04 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=246630

--- Comment #29 from Fabian Keil  ---
As reported in comment 22, the "#define CLANG_SPAWN_CC1 1" change seems to
result in worse results on stable/11 for me.

I've just confirmed this with a system based on r361755: building it on two
systems, one with 2 cpu cores, one with 4, resulted in an unreproducible
/bin/sh, unreproducible rescue binaries and an unreproducible /usr/bin/printf.

Maybe there's a relevant difference between the clang 10.0.0 in stable/11 and
the more recent one in HEAD.

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-bugs@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"


[Bug 233735] Possible build race: genoffset.o /usr/src/sys/sys/types.h: error: machine/endian.h: No such file or directory

2020-06-04 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=233735

Li-Wen Hsu  changed:

   What|Removed |Added

 Status|New |Closed
 Resolution|--- |FIXED

--- Comment #7 from Li-Wen Hsu  ---
Close this for now since this has not happened for more than a year.

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-bugs@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"


[Bug 246981] pkg(8) plugins: configuration settings not provided due to missing object allocation

2020-06-04 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=246981

Bug ID: 246981
   Summary: pkg(8) plugins: configuration settings not provided
due to missing object allocation
   Product: Base System
   Version: 12.1-RELEASE
  Hardware: Any
OS: Any
Status: New
  Severity: Affects Only Me
  Priority: ---
 Component: bin
  Assignee: b...@freebsd.org
  Reporter: ms-freebsd-bugzi...@stoffnet.at

Created attachment 215227
  --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=215227&action=edit
Suggested fix for libpkg/plugins.c and updated examples

Due to a missing allocation of the UCL base object the configuration is parsed
but not provided to the plugin.

See 'pkg.diff' in the attached archive for a suggested fix of libpkg/plugins.c.

Also the examples in the 'pkg-plugins' repository are severely outdated. Please
see the other diff on some improvements, notably of the template and the
zfssnap plugins.

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-bugs@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"


[Bug 246981] pkg(8) plugins: configuration settings not provided due to missing object allocation

2020-06-04 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=246981

Markus Stoff  changed:

   What|Removed |Added

 Attachment #215227|0   |1
is obsolete||
 CC||ms-freebsd-bugzilla@stoffne
   ||t.at

--- Comment #1 from Markus Stoff  ---
Created attachment 215228
  --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=215228&action=edit
Suggested fix for libpkg/plugins.c

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-bugs@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"


[Bug 246981] pkg(8) plugins: configuration settings not provided due to missing object allocation

2020-06-04 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=246981

--- Comment #2 from Markus Stoff  ---
Created attachment 215229
  --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=215229&action=edit
Updated examples in pkg-plugins repository

Diff is based on github repo at https://github.com/freebsd/pkg-plugins/

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-bugs@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"


[Bug 246983] sbput(3) writes out the values of pointers verbatim

2020-06-04 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=246983

Bug ID: 246983
   Summary: sbput(3) writes out the values of pointers verbatim
   Product: Base System
   Version: Unspecified
  Hardware: Any
OS: Any
Status: New
  Severity: Affects Only Me
  Priority: ---
 Component: kern
  Assignee: b...@freebsd.org
  Reporter: goatshit54108@national.shitposting.agency

`struct fs` contains some pointer fields. The binary representation of a
`struct fs` is written out verbatim to the disk: see ffs_sbput() in
sys/ufs/ffs/ffs_subr.c. This inadvertently causes garbage to be stored, in
particular by newfs(1). (It is garbage because those pointers pointed to the
then-current stack or heap.) Although a mere pointer doesn't reveal anything
useful (like a part of a private key) to an attacker, garbage output
deteriorates reproducibility.

In an attempt to work around this design, users of sbput(3) ought to zero out
those pointer fields, but this isn't totally possible, because the function
makes use of the `fs_csp` field. So the solution should be to save the pointers
before writing the whole struct out, and to restore them afterwards.

It would have been ideal if `struct fs` didn't contain any pointers at all.

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-bugs@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"


[Bug 244705] /usr/src/sys/x86/x86/tsc.c: System Clock is 0.3% slow since r352684

2020-06-04 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=244705

Mark Johnston  changed:

   What|Removed |Added

 CC||ma...@freebsd.org

--- Comment #2 from Mark Johnston  ---
Does the problem persist after r359997?

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-bugs@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"


[Bug 246788] make buildworld fails in libc code at /usr/src/lib/libc/gen/ualarm.c:60:3: error: misleading indentation; statement is not part of the previous 'if' [-Werror,-Wmisleading-indentation]

2020-06-04 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=246788

Mark Johnston  changed:

   What|Removed |Added

 CC||ma...@freebsd.org

--- Comment #2 from Mark Johnston  ---
(In reply to Ulas SAYGIN from comment #1)
There seems to be something strange with your environment, the change in
question was committed to svn months ago.  The github repo is just a mirror of
the svn repo, so presumably there is something wrong with your svn checkout. 
Do you see any build errors using a fresh checkout?

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-bugs@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"


[Bug 246788] make buildworld fails in libc code at /usr/src/lib/libc/gen/ualarm.c:60:3: error: misleading indentation; statement is not part of the previous 'if' [-Werror,-Wmisleading-indentation]

2020-06-04 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=246788

--- Comment #3 from Mark Johnston  ---
*** Bug 246801 has been marked as a duplicate of this bug. ***

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-bugs@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"


[Bug 246788] make buildworld fails in libc code at /usr/src/lib/libc/gen/ualarm.c:60:3: error: misleading indentation; statement is not part of the previous 'if' [-Werror,-Wmisleading-indentation]

2020-06-04 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=246788

--- Comment #4 from Mark Johnston  ---
*** Bug 246797 has been marked as a duplicate of this bug. ***

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-bugs@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"


[Bug 246797] make buildworld fails in rtld-elf code at /usr/src/libexec/rtld-elf/rtld.c:1175:20: error: no member named 'l_refname' in 'struct link_map'; did you mean 'l_name'?

2020-06-04 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=246797

Mark Johnston  changed:

   What|Removed |Added

 Resolution|--- |DUPLICATE
 CC||ma...@freebsd.org
 Status|New |Closed

--- Comment #2 from Mark Johnston  ---


*** This bug has been marked as a duplicate of bug 246788 ***

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-bugs@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"


[Bug 246801] make buildworld error code at /usr/src/lib/libc/gen/auxv.c:89:8: error: use of undeclared identifier 'AT_BSDFLAGS' case AT_BSDFLAGS:

2020-06-04 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=246801

Mark Johnston  changed:

   What|Removed |Added

 Status|New |Closed
 CC||ma...@freebsd.org
 Resolution|--- |DUPLICATE

--- Comment #2 from Mark Johnston  ---


*** This bug has been marked as a duplicate of bug 246788 ***

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-bugs@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"


[Bug 246080] vt options mismatch

2020-06-04 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=246080

--- Comment #4 from commit-h...@freebsd.org ---
A commit references this bug:

Author: markj
Date: Thu Jun  4 16:05:25 UTC 2020
New revision: 361792
URL: https://svnweb.freebsd.org/changeset/base/361792

Log:
  Update vt(4) config option names to chase r303043.

  PR:   246080
  Submitted by: David Marec 
  MFC after:1 week

Changes:
  head/share/man/man4/vt.4
  head/sys/conf/NOTES
  head/sys/conf/options

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-bugs@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"


[Bug 246080] vt options mismatch

2020-06-04 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=246080

Mark Johnston  changed:

   What|Removed |Added

 Status|New |In Progress
   Assignee|b...@freebsd.org|ma...@freebsd.org
 CC||ma...@freebsd.org

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-bugs@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"


[Bug 246985] `newfs -R` is incomplete

2020-06-04 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=246985

Bug ID: 246985
   Summary: `newfs -R` is incomplete
   Product: Base System
   Version: Unspecified
  Hardware: Any
OS: Any
Status: New
  Severity: Affects Only Me
  Priority: ---
 Component: kern
  Assignee: b...@freebsd.org
  Reporter: goatshit54108@national.shitposting.agency

`newfs -R` has the purpose of enforcing reproducible output, i.e. to be
independent of time or random seeds. However, it is incomplete, because
sbput(3) writes a fresh time() sample into the `struct fs` variable: see
ffs_sbput() in sys/ufs/ffs/ffs_subr.c.

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-bugs@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"


[Bug 246986] userboot.so can't open rootfs partition if you use raw BSD partitions directly on disk without any slices

2020-06-04 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=246986

Bug ID: 246986
   Summary: userboot.so can't open rootfs partition if you use raw
BSD partitions directly on disk without any slices
   Product: Base System
   Version: 12.1-STABLE
  Hardware: amd64
OS: Any
Status: New
  Severity: Affects Many People
  Priority: ---
 Component: bin
  Assignee: b...@freebsd.org
  Reporter: mi...@elwix.org

Created attachment 215231
  --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=215231&action=edit
Patch for disk_open()

>From FreeBSD 12.1 till current version of FreeBSD. userboot.so loader haves
issue with raw BSD partitions directly on disk without any PC slice schema aka
MBR or GPT.

Bug came after commit, when predefine constant values was replaced with macro
definitions in userboot/main.c and common/disk.c. These two members of devsw
structure d_slice and d_partition now have defined constants. One of them have
different value from previous version of code.
D_PARTWILD now have value -2, before that change dev.d_partition has 0.

I didn't take easy step directly to change macro D_PARTWILD to 0, because I saw
that uboot loader already used this macro.
I made patch in common/disk.c file into disk_open() function

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-bugs@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"


[Bug 246630] stable/11 regression: base.txz reproducibility depends on number of cpu cores

2020-06-04 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=246630

--- Comment #30 from Dimitry Andric  ---
(In reply to Fabian Keil from comment #29)
That's very strange. I could fairly easily reproduce the different printf.o
output by building either with "make -j2", or with "make" on the same machine. 

Since "make -j" appears to mess around with ttys and stderr, it could explain
the slightly different memory contents of the program at startup. In any case,
removing the integrated cc1 stage always resulted in the same printf.o output.

Are you saying you ran the same build on different machines? Are you 100% sure
that all the includes pulled into printf.c were exactly the same? Is there any
way you can do a sha256sum of the .i files?


> Maybe there's a relevant difference between the clang 10.0.0 in stable/11 and 
> the more recent one in HEAD.

I don't think so, head has 10.0.1-rc1, but it showed precisely the effects I
mentioned before. Disabling integrated cc1 fixed it for me.

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-bugs@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"


[Bug 246983] sbput(3) writes out the values of pointers verbatim

2020-06-04 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=246983

Brooks Davis  changed:

   What|Removed |Added

 CC||bro...@freebsd.org

--- Comment #1 from Brooks Davis  ---
In CheriBSD's cheri-purecap-kernel branch
(https://github.com/CTSRD-CHERI/cheribsd/tree/cheri-purecap-kernel) we have a
modification that reduces this to a single pointer to a structure holding the
other pointers.  In our case this is because the in-kernel use includes too
many pointers to fit when you blow them up to 128-bit.  This doesn't address
the leakage issues, but might be a place to start from.

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-bugs@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"


[Bug 244852] Crash in sysctl(3) after call to "sysctl -a | grep ..."

2020-06-04 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=244852

Mark Johnston  changed:

   What|Removed |Added

 CC||ma...@freebsd.org

--- Comment #1 from Mark Johnston  ---
Do you have a vmcore still available?  Is the problem reproducible?

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-bugs@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"


[Bug 245289] Gwenview misrenders high resolution .TIF files

2020-06-04 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=245289

Mark Johnston  changed:

   What|Removed |Added

 Resolution|--- |Not Accepted
 CC||ma...@freebsd.org
 Status|New |Closed

--- Comment #1 from Mark Johnston  ---
This doesn't have anything to do with the FreeBSD base system.  Please file a
bug against the corresponding port, if you suspect the problem is
FreeBSD-specific, or against the upstream project.

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-bugs@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"


[Bug 244852] Crash in sysctl(3) after call to "sysctl -a | grep ..."

2020-06-04 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=244852

--- Comment #2 from Juraj Lutter  ---
No, I do not have vmcore. Whether the problem is reproducible, I can not tell
right now as the server is in production and possible downtime has to be
scheduled. I will try to arrange it and come back once the vmcore will be
available (if the system will panic.)

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-bugs@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"


[Bug 246983] sbput(3) writes out the values of pointers verbatim

2020-06-04 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=246983

--- Comment #2 from goatshit54108@national.shitposting.agency ---
Created attachment 215239
  --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=215239&action=edit
in ffs_sbput(), clear the pointers for the duration of writing

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-bugs@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"


[Bug 246983] sbput(3) writes out the values of pointers verbatim

2020-06-04 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=246983

Mark Linimon  changed:

   What|Removed |Added

   Keywords||patch
   Assignee|b...@freebsd.org|f...@freebsd.org

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-bugs@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"


[Bug 246046] boot error in boot/lua/drawer.lua

2020-06-04 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=246046

--- Comment #7 from commit-h...@freebsd.org ---
A commit references this bug:

Author: kevans
Date: Fri Jun  5 02:52:07 UTC 2020
New revision: 361817
URL: https://svnweb.freebsd.org/changeset/base/361817

Log:
  MFC r361709: lualoader: improve drawer error handling

  At least one user has landed in a scenario where logo files appear to be
  misnamed, and we failed to find them. Our fallback for missing logodefs is
  orb/orbbw, based on the color status. In a scenario where we can't locate
  the logos, though, this is not ideal. Add in one more layer of fallback
  to properly just don't draw any logo if the fan has been jam packed with
  foreign material.

  PR:   246046

Changes:
_U  stable/11/
  stable/11/stand/lua/drawer.lua
_U  stable/12/
  stable/12/stand/lua/drawer.lua

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-bugs@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"


[Bug 246046] boot error in boot/lua/drawer.lua

2020-06-04 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=246046

Kyle Evans  changed:

   What|Removed |Added

   Assignee|b...@freebsd.org|kev...@freebsd.org
 Resolution|--- |FIXED
 Status|In Progress |Closed
 CC||b...@freebsd.org

--- Comment #8 from Kyle Evans  ---
This should no longer degenerate into a failure to boot on both stable
branches. Thanks for the report!

I'm closing this as FIXED, but of course feel free to re-open it or comment if
you feel that it's not been sufficiently addressed.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
You are the assignee for the bug.
___
freebsd-bugs@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"


[Bug 246046] boot error in boot/lua/drawer.lua

2020-06-04 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=246046

Kyle Evans  changed:

   What|Removed |Added

  Flags|mfc-stable12?,  |mfc-stable12+,
   |mfc-stable11?   |mfc-stable11+

-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
freebsd-bugs@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"


[Bug 246940] [wishlist/enhancement, patch incl.]: idle user tasks should be charged as "nice" or "idle" CPU time

2020-06-04 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=246940

t.eichsta...@gmx.net changed:

   What|Removed |Added

 Attachment #215172|0   |1
is obsolete||
 Attachment #215173|0   |1
is obsolete||

--- Comment #8 from t.eichsta...@gmx.net ---
Created attachment 215241
  --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=215241&action=edit
expose add. cp_time(s) (realtime/idle) via sysctl cp_time(s)_ext

Now guess what, that was so simple that it succeeded to compile on the 3rd try
(only typos), and it runs on bare metal on the 1st -- I'm writing this with the
patch applied.  I was too lazy to beadm or set up a VM to test.

If I violated any written or unspoken guidelines/rules, please let me know
(PLMK).
The Dev Handbook is on top of my list to read, but for now I just followed what
I saw in the src code.

I took the freedom to add some comments and documentation which might write out
what is already clear to the avg audience.  If so, PLMK, and I'll fix all that.
 I want to do it the BSD way, and no quick hack.

In pcpu.h:struct pcpu{}, I added "long pc_cp_time_ext[CPUSTATES_EXT]" analogue
to "pc_cp_time[CPUSTATES]", and I'm not comfortable with that.  It will break
some base and port apps, right? top(1) runs... but others?

Strictly speaking, a new sysctl is not neccessary, as I also added
resource.h:read_cpu_time_ext() analogue to read_cpu_time().  IMHO it's kind to
have a sysctl, because curious folk who will make use out of it, will stumble
over this more likely than if it's hidden in a header file.

Now if you approve this patch, I can start patching powerd(8) to make use of
it, but I fear to start an avalanche, esp. concerning supporting freq setting
on independant cpu.  It also seems fairly simple, though.

thx again for your time.

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-bugs@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"


[Bug 246981] pkg(8) plugins: configuration settings not provided due to missing object allocation

2020-06-04 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=246981

Markus Stoff  changed:

   What|Removed |Added

  Component|bin |Package Infrastructure
Version|12.1-RELEASE|Latest
Product|Base System |Ports & Packages

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-bugs@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"