[Bug 267871] /usr/bin/rs compile fails after udate to c++
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=267871 Herbert J. Skuhra changed: What|Removed |Added CC||herb...@gojira.at --- Comment #1 from Herbert J. Skuhra --- Is your src checkout in sync and clean? What's the output of git rev-parse HEAD git status git diff in src? uname -a? -- You are receiving this mail because: You are the assignee for the bug.
[Bug 266879] fusefs, net/glusterfs: GlusterFS mount not handled as expected
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=266879 --- Comment #26 from Alan Somers --- (In reply to David from comment #25) As I explained before, you can do it by setting vfs.fusefs.data_cache_mode=0. But that only works for fusefs daemons using protocol level 7.22 or below. For higher protocol levels, the daemon must do it itself. -- You are receiving this mail because: You are the assignee for the bug.
[Bug 267871] /usr/bin/rs compile fails after udate to c++
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=267871 --- Comment #2 from rkober...@gmail.com --- (In reply to Herbert J. Skuhra from comment #1) # git rev-parse HEAD 424bf1d5ca5bdba0597b546ec3931eb05bfabcab # git status On branch main Your branch is up to date with 'origin/main'. nothing to commit, working tree clean # git diff # -- You are receiving this mail because: You are the assignee for the bug.
[Bug 266145] [Intel Alder Lake] Crashes on CURRENT vfs
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=266145 Konstantin Belousov changed: What|Removed |Added CC||k...@freebsd.org --- Comment #9 from Konstantin Belousov --- Created attachment 238192 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=238192&action=edit Current experimental workaround -- You are receiving this mail because: You are the assignee for the bug.
[Bug 267871] /usr/bin/rs compile fails after udate to c++
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=267871 --- Comment #3 from Herbert J. Skuhra --- Do you build with NO_CLEAN/WITHOUT_CLEAN? Does it work if you run: cd /usr/src/usr.bin/rs make cleandir or wipe /usr/obj? Here it works: --- rs.o --- c++ -target x86_64-unknown-freebsd14.0 --sysroot=/usr/obj/usr/src/amd64.amd64/tmp -B/usr/obj/usr/src/amd64.amd64/tmp/usr/bin -O2 -pipe -fno-common -fPIE -mretpoline -MD -MF.depend.rs.o -MTrs.o -Wno-format-zero-length -fstack-protector-strong -Wsystem-headers -Werror -Wall -Wno-format-y2k -W -Wno-unused-parameter -Wpointer-arith -Wreturn-type -Wcast-qual -Wwrite-strings -Wswitch -Wshadow -Wunused-parameter -Wcast-align -Wchar-subscripts -Wmissing-variable-declarations -Wthread-safety -Wno-empty-body -Wno-string-plus-int -Wno-unused-const-variable -Wno-error=unused-but-set-variable -Qunused-arguments -fPIE -mretpoline -Wno-c++11-extensions -c /usr/src/usr.bin/rs/rs.cc -o rs.o -- You are receiving this mail because: You are the assignee for the bug.
[Bug 267871] /usr/bin/rs compile fails after udate to c++
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=267871 --- Comment #4 from rkober...@gmail.com --- (In reply to Herbert J. Skuhra from comment #3) Build was "nice make -j12 buildworld" Did not delete existing /usr/obj. Since last update on 11/8, I just did: # git pull --ff-only # nice make -j12 buildworld Today, after cleandir in usr.bin/rs, I did: # make -j12 -DNO_CLEAN buildworld This completed successfully. No idea what the cleandir did, bur some depend or config file must have survived the cleaning in the initial buildworld. Unless there are additional reports in the next day or two, I'll close the ticket. -- You are receiving this mail because: You are the assignee for the bug.
[Bug 259090] UFS: bad file descriptor: soft update journaling can not be enabled on some FreeBSD-provided disk images – failed to write updated cg
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=259090 --- Comment #12 from commit-h...@freebsd.org --- A commit in branch stable/13 references this bug: URL: https://cgit.FreeBSD.org/src/commit/?id=bca262f0f351e3881d478b7a9764c91ccb83c260 commit bca262f0f351e3881d478b7a9764c91ccb83c260 Author: Kirk McKusick AuthorDate: 2022-11-12 23:36:07 + Commit: Kirk McKusick CommitDate: 2022-11-20 17:13:49 + Fix for tunefs(8) unable to add a UFS/FFS soft update journal. The reported bug is UFS: bad file descriptor: soft update journaling can not be enabled on some FreeBSD-provided disk images – failed to write updated cg. The UFS library (libufs(3)) failed to reopen its disk descriptor when first attempting to update a cylinder group. The error only occurred when trying to add journaling to a filesystem whose first cylinder group was too full to hold the journal. PR: 259090 MFC after:1 week Sponsored by: The FreeBSD Foundation (cherry picked from commit 5c7ba6bdf83fda82cce70f384e2ec8218f13002e) lib/libufs/cgroup.c | 4 1 file changed, 4 insertions(+) -- You are receiving this mail because: You are the assignee for the bug.
[Bug 267654] UFS "cylinder checksum failed" on temporary storage or data disk on arm64 vm in Azure
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=267654 --- Comment #11 from Kirk McKusick --- I do not have any better idea than the debugging idea that you are suggesting. Of interest is verifying that the seek offset is correct and that the checksum of what is written and what ends up on the disk match. Note that the checksum is being calculated and the block written in the libufs routine lib/libufs/cgroup.c. See functions cgwrite(), cgwrite1(), and where the work is actually done cgput(). -- You are receiving this mail because: You are the assignee for the bug.
[Bug 266145] [Intel Alder Lake] Crashes on CURRENT vfs
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=266145 --- Comment #10 from rkober...@gmail.com --- Can I assume that, with this patch, I should re-enable PCID? Building new kernel now. Will report any issues I see. -- You are receiving this mail because: You are the assignee for the bug.
[Bug 259090] UFS: bad file descriptor: soft update journaling can not be enabled on some FreeBSD-provided disk images – failed to write updated cg
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=259090 Kirk McKusick changed: What|Removed |Added Resolution|--- |FIXED Status|In Progress |Closed --- Comment #13 from Kirk McKusick --- Has been MFC'ed to 13. Not relevant to 12. -- You are receiving this mail because: You are the assignee for the bug.
[Bug 102502] [netgraph] [patch] ifconfig name does't rename netgraph node in network.subr
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=102502
Aleksandr Fedorov changed:
What|Removed |Added
CC||afedo...@freebsd.org
--- Comment #7 from Aleksandr Fedorov ---
I think thi bug should be closed.
root@xenon:/home/XeNoN # ifconfig tap create
tap0
root@xenon:/home/XeNoN # ngctl ls
There are 5 total nodes:
Name: ngeth0 Type: eiface ID: 0002 Num hooks: 1
Name: ngeth1 Type: eiface ID: 0004 Num hooks: 1
Name: re0 Type: ether ID: 0006 Num hooks: 0
Name: tap0Type: ether ID: 000a Num hooks: 0
Name: ngctl44711 Type: socket ID: 000b Num hooks: 0
root@xenon:/home/XeNoN # ifconfig tap0 name renamed0
renamed0
root@xenon:/home/XeNoN # ngctl ls
There are 5 total nodes:
Name: ngeth0 Type: eiface ID: 0002 Num hooks: 1
Name: ngeth1 Type: eiface ID: 0004 Num hooks: 1
Name: re0 Type: ether ID: 0006 Num hooks: 0
Name: renamed0Type: ether ID: 000a Num hooks: 0
Name: ngctl44841 Type: socket ID: 000c Num hooks: 0
root@xenon:/home/XeNoN #
ng_ether:
*
* Interface arrival notification handler.
* The notification is produced in two cases:
* o a new interface arrives
* o an existing interface got renamed
* Currently the first case is handled by ng_ether_attach via special
* hook ng_ether_attach_p.
*/
static void
ng_ether_ifnet_arrival_event(void *arg __unused, struct ifnet *ifp)
{
char name[IFNAMSIZ];
node_p node;
/* Only ethernet interfaces are of interest. */
if (ifp->if_type != IFT_ETHER &&
ifp->if_type != IFT_L2VLAN &&
ifp->if_type != IFT_BRIDGE)
return;
/*
* Just return if it's a new interface without an ng_ether companion.
*/
node = IFP2NG(ifp);
if (node == NULL)
return;
/* Try to give the node the same name as the new interface name */
ng_ether_sanitize_ifname(ifp->if_xname, name);
if (ng_name_node(node, name) != 0)
log(LOG_WARNING, "%s: can't re-name node %s\n", __func__,
name);
}
--
You are receiving this mail because:
You are the assignee for the bug.
[Bug 262492] Update resolv.conf(5) "not necessary" language
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=262492 Pau Amma changed: What|Removed |Added Status|New |Open Assignee|b...@freebsd.org|paua...@freebsd.org -- You are receiving this mail because: You are the assignee for the bug.
[Bug 267884] kadmind can read beyond the end of an incoming message's buffer
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=267884
Bug ID: 267884
Summary: kadmind can read beyond the end of an incoming
message's buffer
Product: Base System
Version: CURRENT
Hardware: Any
OS: Any
Status: New
Severity: Affects Some People
Priority: ---
Component: bin
Assignee: b...@freebsd.org
Reporter: r...@lcs.mit.edu
Attachment #238198 text/plain
mime type:
Created attachment 238198
--> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=238198&action=edit
send a non-null-terminated appl_version to kadmind
kadmind's handle_v5() calls krb_recvauth_match_version(), which
contains:
n = krb5_net_read (context, p_fd, &len, 4);
...;
len = ntohl(len);
her_appl_version = malloc (len);
if (krb5_net_read (context, p_fd, her_appl_version, len) != len
|| !(*match_appl_version)(match_data, her_appl_version)) {
repl = 2;
krb5_net_write (context, p_fd, &repl, 1);
krb5_set_error_message(context, KRB5_SENDAUTH_BADAPPLVERS,
N_("wrong sendauth version (%s)", ""),
her_appl_version);
The code does not check that the incoming message in her_appl_version
is null terminated, which can cause trouble for match_appl_version()'s
call to sscanf, and krb5_set_error_message's use of her_apply_version.
This is with CURRENT source from today (Nov 20 2022).
I've attached a demo. Since there's often a null somewhere soon after
the end of the allocated buffer, the problem is only reliably visible
with something like valgrind:
# /usr/libexec/kadmind --version
kadmind (Heimdal 1.5.2)
Copyright 1995-2011 Kungliga Tekniska Högskolan
Send bug-reports to heimdal-b...@h5l.org
# valgrind /usr/libexec/kadmind --debug &
# cc kadmind3a.c
# ./a.out
==67648== Memcheck, a memory error detector
==67648== Copyright (C) 2002-2022, and GNU GPL'd, by Julian Seward et al.
==67648== Using Valgrind-3.19.0 and LibVEX; rerun with -h for copyright info
==67648== Command: /usr/libexec/kadmind --debug
==67648==
==67648== Invalid read of size 1
==67648==at 0x4852EE9: strlen (in
/usr/local/libexec/valgrind/vgpreload_memcheck-amd64-freebsd.so)
==67648==by 0x4A596BC: vsscanf (in /lib/libc.so.7)
==67648==by 0x4A4C72C: sscanf (in /lib/libc.so.7)
==67648==by 0x112677: ??? (in /usr/libexec/kadmind)
==67648==by 0x4907BE6: krb5_recvauth_match_version (in
/usr/lib/libkrb5.so.11)
==67648==by 0x1114CD: ??? (in /usr/libexec/kadmind)
==67648==by 0x112978: ??? (in /usr/libexec/kadmind)
==67648==by 0x10D16C: ??? (in /usr/libexec/kadmind)
==67648==by 0x4823007: ???
==67648== Address 0x5b463b6 is 0 bytes after a block of size 150 alloc'd
==67648==at 0x484C8A4: malloc (in
/usr/local/libexec/valgrind/vgpreload_memcheck-amd64-freebsd.so)
==67648==by 0x4907BA9: krb5_recvauth_match_version (in
/usr/lib/libkrb5.so.11)
==67648==by 0x1114CD: ??? (in /usr/libexec/kadmind)
==67648==by 0x112978: ??? (in /usr/libexec/kadmind)
==67648==by 0x10D16C: ??? (in /usr/libexec/kadmind)
==67648==by 0x4823007: ???
--
You are receiving this mail because:
You are the assignee for the bug.
Problem reports for b...@freebsd.org that need special attention
To view an individual PR, use: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=(Bug Id). The following is a listing of current problems submitted by FreeBSD users, which need special attention. These represent problem reports covering all versions including experimental development code and obsolete releases. Status |Bug Id | Description +---+--- New |197876 | [devfs] an error in devfs leads to data loss and New |198797 | [PATCH] Added an option to install BSDstats to bs New |202362 | ntp: restore refclocks selection (10.2-RELEASE re New |202740 | vi/ex string substitution problem when there is m New |204097 | witness_initialize() does not perform bound check New |206336 | [patch] usr.sbin/freebsd-update allow proxy confi New |209213 | UEFI Loader shows only black screen with Nvidia G New |210804 | installerconfig - using ZFS create in custom scri New |223470 | freebsd-update: Cannot identify running kernel (/ New |230620 | "install -d" issue New |235085 | [PATCH] Option to make rc.d/sysctl more verbose ( New |252123 | fetch(3): Fix wrong usage of proxy when request i Open|177821 | sysctl: Some security.jail nodes are funky, dupli Open|182466 | [headers] [patch] make self-contained Open|183618 | [panic] Dell PowerEdge R620 -- PERC H710 Mini (mf Open|192573 | Add ps(1) option: Print process start time in sec Open|194925 | [pf] [ifconfig] interface group keywords do not w Open|197921 | scheduler: Allow non-migratable threads to bind t Open|206528 | Emulex LPe 16002 FC HBA Not Recognized by oce(4) Open|206649 | cyapa(4): Add common gestures for Cypress APA I2C Open|207940 | stand/efi/boot1: Add boot partition selection Open|212608 | sockstat(1) and lsof(8) can not identity the owne Open|220246 | syslogd does not send RFC3164-conformant messages Open|221305 | Mouse cursor loss when moving cursor while loadin Open|221550 | kern.bootfile returns only /kernel on mips64 (ERL Open|221854 | makefs: Reject UFS labels that are too long to fi Open|226893 | freebsd-update: Support patchlevel argument for f Open|231810 | [build] release always fails with "mkimg: partiti Open|233578 | Unprivileged local user can prevent other users l Open|233988 | freebsd-update: Improve progress output on termin Open|236718 | system panics with message: vm_fault_hold: fault Open|237287 | moused(8) ignores button release events in virtua Open|237924 | Possible infinite loop in function empty_aux_buff Open|238183 | cam/scsi/scsi_sa.c: warnings issued by static ana Open|238486 | Possible buffer overflow bug in sc_allocate_keybo Open|238550 | Touchpad (via SMBus) not working: Synaptics (SYN1 Open|238638 | mfi: Remove unnecessary pointer printing in mfi.c Open|238837 | init: Remove P_SYSTEM flag from PID 1 to allow ea Open|241697 | i915kms: Kernel panic loading module on custom ke Open|247132 | Fix build error: use of undeclared identifier 'cp Open|248352 | mfi(4): Remove RAID map sync functionality Open|257149 | CFLAGS not passed to whole build New |260138 | TPM2 Support in bootloader / kernel in order to r New |262957 | mpr(4), mps(4): change formally to formerly New |267537 | contrib/nvi: Fix core dump when tags file pattern Open|179832 | manual page of mac_from_text suggests incorrect f 46 problems total for which you should take action.
[Bug 216111] Minor violation of style(9) in hash.h
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=216111 --- Comment #1 from statistisches_avar...@simplelogin.com --- Created attachment 238205 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=238205&action=edit Proposed patch for 216111 -- You are receiving this mail because: You are the assignee for the bug.
