[Bug 276316] Issue with sharenfs property on an encrypted ZFS zvol.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=276316 Bug ID: 276316 Summary: Issue with sharenfs property on an encrypted ZFS zvol. Product: Base System Version: 14.0-RELEASE Hardware: arm64 OS: Any Status: New Severity: Affects Only Me Priority: --- Component: kern Assignee: b...@freebsd.org Reporter: dmil...@me.com I have an encrypted zvol called "Copies/Vault". One of its properties is "sharenfs" - used for NFS sharing. The issue is… I change that property the third or fourth time in the last 2 days. It should keep the new value, but instead, it turns the value back to an old IP. This is how I modify that property: `zfs set sharenfs="casie.home" Copies/Vault` - after the change, I restart the mountd service and it works normally. Except that later it will switch that property back to that old IP again and I lose access to my NFS share. I did a few reboots of that machine if that matters. Any ideas why? Thanks -- You are receiving this mail because: You are the assignee for the bug.
[Bug 276326] find: Allow '/' to be used with -perm for GNU compatibility
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=276326 Bug ID: 276326 Summary: find: Allow '/' to be used with -perm for GNU compatibility Product: Base System Version: 14.0-STABLE Hardware: Any OS: Any Status: New Severity: Affects Only Me Priority: --- Component: bin Assignee: b...@freebsd.org Reporter: rbra...@suse.com Since 2005 GNU find(1) no longer allows '+' to be used with -perm, forcing the use of a / instead. This PR adds support for this character as synonym for '+': https://github.com/freebsd/freebsd-src/pull/1060 -- You are receiving this mail because: You are the assignee for the bug.
[Bug 193339] syscons: mouse reporting works properly only on ttyv0
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=193339 Warner Losh changed: What|Removed |Added Status|Open|In Progress Assignee|b...@freebsd.org|i...@freebsd.org CC||i...@freebsd.org -- You are receiving this mail because: You are the assignee for the bug.
[Bug 275536] Wired memory leak
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=275536 --- Comment #2 from Mark Johnston --- Are you still seeing this problem in 14.0-p3? The bug described in comment 1 is fixed there. -- You are receiving this mail because: You are the assignee for the bug.
[Bug 268653] /src/sys/dev/hyperv/input/hv_kbd.c error: use of undeclared identifier 'keycode'
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=268653 Joerg Wunsch changed: What|Removed |Added CC||jo...@freebsd.org, ||w...@freebsd.org --- Comment #8 from Joerg Wunsch --- (In reply to holmez from comment #6) More precisely, hyperv enabled but no evdev enabled. The #ifdev EVDEV_SUPPORT around the definition of "keycode" has already been removed in commit 55eb41bb1fb69429 by Vladimir Kondratyev on 2021-04-23. Seems he forgot to MFC that fix. I'm adding him to the Cc list. -- You are receiving this mail because: You are the assignee for the bug.
[Bug 276316] Issue with sharenfs property on an encrypted ZFS zvol.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=276316 Mark Linimon changed: What|Removed |Added Assignee|b...@freebsd.org|f...@freebsd.org -- You are receiving this mail because: You are the assignee for the bug.
[Bug 144325] [libpcap] tcpdump compiles complex expression to incorrect BPF code
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=144325 Warner Losh changed: What|Removed |Added CC||i...@freebsd.org --- Comment #8 from Warner Losh --- Since the import of 1.10.3, this patch conflicts. I don't know if the changes related to detecting the optimizer loop or not will fix this issue though. Can you confirm either that (a) the upstream fix in 1.10.3 fixes your issue or (b) making the trivial modifications to your patch will fix the still lingering issue? I see that the upstream pull request remains open, so I'm unsure what the status is... The import was just a couple of weeks after the last comment... Thanks and sorry for the delay. -- You are receiving this mail because: You are the assignee for the bug.
[Bug 158707] [panic] kernel trap 12 with interrupts disabled
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=158707 Warner Losh changed: What|Removed |Added Status|Open|Closed CC||i...@freebsd.org Resolution|--- |FIXED --- Comment #3 from Warner Losh --- Closing this bug. Due to its age and lack of stack traceback or reproduction instructions and the large number of changes that have gone into FreeBSD without wide-spread reporting of this issue. Should this still be persisting in FreeBSD 13 or newer, please open a new bug and our new bug triage will handle it in a more timely manner. -- 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 |252123 | fetch(3): Fix wrong usage of proxy when request i New |262764 | After DVD1 13.0-R install with ports tree, portsn New |262989 | sys/conf/files, sys/conf/options, sys/conf/NOTES: New |269994 | build options have different kernel and userland Open| 46441 | sh(1): Does not support PS1, PS2, PS4 parameter e Open|165059 | vtnet(4): Networking breaks with a router using v Open|177821 | sysctl: Some security.jail nodes are funky, dupli Open|220246 | syslogd does not send RFC3164-conformant messages Open|232914 | kern/kern_resource: Integer overflow in function Open|250309 | devmatch: panic: general protection fault: sysctl Open|255130 | Issue with rtsx driver Open|256952 | kqueue(2): Improve epoll Linux compatibility (com Open|257646 | opensm: rc service is installed by default, but o Open|258665 | lib/libfetch: Add Happy Eyeballs (RFC8305) suppor Open|259292 | vmware/pvscsi: UNMAP fails on VMWare 6.7 thinly p Open|259636 | multiple components: Change "Take Affect" to "Tak Open|259640 | snd_hda(4): Fix sound output in Lenovo Ideapad 33 Open|259655 | periodic: security/security.functions does not re Open|259703 | In sys/dev/pci/pci.c, error in do_power_nodriver Open|259808 | etc/periodic/daily/100.clean-disks: Fix error (Di Open|260214 | acpi_battery: Should provide current/max battery Open|260245 | swap/vm: Apparent memory leak: 100% swap usage Open|261640 | sysctl: Add -F option to display sysctl format st Open|261641 | drm-kmod: Launch message is written into (possibl Open|261771 | nvme(4): Reports errors every 5 minutes: PRP OFFS Open|261971 | kernel crash launching bhyve guest on ZFS: #15 bu Open|262157 | su+j: Crashes during mmc(4) fsck after timeout: E Open|262192 | Crashes at boot with kern.random.initial_seeding. Open|264028 | loader: Incorrect (32gb) memory reported by BTX l Open|264075 | freebsd-update in 13.1-RELEASE detects an install Open|264188 | kinit(1): Ignores KRB5CCNAME environment variable Open|264226 | setting kern.vty=sc causes hang during UEFI boot Open|264757 | fetch: Show correct port number in -vv output Open|264833 | 12.3-STABLE panic on sync and reboot: panic: slee Open|266419 | mrsas: Corrupts memory (crashes) when reading dat 35 problems total for which you should take action.
[Bug 276341] zfs panic: VERIFY3(rc->rc_count == number) failed
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=276341
Bug ID: 276341
Summary: zfs panic: VERIFY3(rc->rc_count == number) failed
Product: Base System
Version: 15.0-CURRENT
Hardware: Any
OS: Any
Status: New
Keywords: crash
Severity: Affects Only Me
Priority: ---
Component: kern
Assignee: b...@freebsd.org
Reporter: j...@mit.edu
I rebooted a system running CURRENT from late December to update to today's
CURRENT and it crashed while unloading ZFS.
panic: VERIFY3(rc->rc_count == number) failed (262144 == 0)
cpuid = 0
time = 1705275564
KDB: stack backtrace:
db_trace_self() at db_trace_self
db_trace_self_wrapper() at db_trace_self_wrapper+0x38
vpanic() at vpanic+0x1a4
spl_panic() at spl_panic+0x44
zfs_refcount_destroy_many() at zfs_refcount_destroy_many+0xdc
arc_fini() at arc_fini+0x274
dmu_fini() at dmu_fini+0xc
spa_fini() at spa_fini+0x34
zfs_kmod_fini() at zfs_kmod_fini+0x78
zfs_shutdown() at zfs_shutdown+0x40
kern_reboot() at kern_reboot+0x574
sys_reboot() at sys_reboot+0x350
do_el0_sync() at do_el0_sync+0x58c
handle_el0_sync() at handle_el0_sync+0x48
--- exception, esr 0x5600
[...]
#9 0x0003daf8 in spl_panic (file=,
func=, line=13227925,
fmt=0x12 )
at /usr/src/sys/contrib/openzfs/module/os/freebsd/spl/spl_misc.c:100
ap = {__stack = 0xf39d5630, __gr_top = 0xf39d55e0,
__vr_top = 0xa10a92a0, __gr_offs = -32, __vr_offs = 0}
#10 0x001633e0 in zfs_refcount_destroy_many (rc=,
number=18446462598740100184)
at /usr/src/sys/contrib/openzfs/module/zfs/refcount.c:98
_verify3_right = 18446462598740100184
_verify3_left = 115
cookie = 0x0
ref =
#11 0x001633fc in zfs_refcount_destroy (rc=0x12,
rc@entry=0x010e7a80 )
at /usr/src/sys/contrib/openzfs/module/zfs/refcount.c:112
No locals.
#12 0x000c0508 in arc_state_fini ()
at /usr/src/sys/contrib/openzfs/module/zfs/arc.c:7421
No locals.
#13 arc_fini () at /usr/src/sys/contrib/openzfs/module/zfs/arc.c:7753
p =
#14 0x000ee4d0 in dmu_fini ()
at /usr/src/sys/contrib/openzfs/module/zfs/dmu.c:2549
No locals.
#15 0x00189dd8 in spa_fini ()
at /usr/src/sys/contrib/openzfs/module/zfs/spa_misc.c:2549
No locals.
#16 0x001e67ac in zfs_kmod_fini ()
at /usr/src/sys/contrib/openzfs/module/zfs/zfs_ioctl.c:7933
zsnext = 0x0
zs = 0x0
#17 0x0006e654 in zfs__fini ()
at /usr/src/sys/contrib/openzfs/module/os/freebsd/zfs/kmod_core.c:284
No locals.
#18 zfs_shutdown (arg=, howto=)
at /usr/src/sys/contrib/openzfs/module/os/freebsd/zfs/kmod_core.c:297
No locals.
#19 0x00693158 in kern_reboot (howto=0)
at /usr/src/sys/kern/kern_shutdown.c:517
_ep = 0xa2f63c40
_t = 0xa2f63c40
_el = 0xa1709c80
once = 1
#20 0x00692b74 in sys_reboot (td=0x000121c2a640,
uap=0x000121c2aa40) at /usr/src/sys/kern/kern_shutdown.c:312
error =
#21 0x00a60060 in syscallenter (td=0x000121c2a640)
at /usr/src/sys/arm64/arm64/../../kern/subr_syscall.c:186
se = 0x00fa1378
sa = 0x000121c2aa30
p =
error =
sy_thr_static = true
traced =
_audit_entered =
My kernel configuration file is
include GENERIC
ident STRIATUS
nooptions WITNESS
nooptions WITNESS_SKIPSPIN
options ZFS
The kernel that crashed had changes on main up to 5bc10feacc9d.
--
You are receiving this mail because:
You are the assignee for the bug.
[Bug 276341] zfs panic: VERIFY3(rc->rc_count == number) failed
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=276341 Mark Johnston changed: What|Removed |Added Status|New |Open CC||ma...@freebsd.org, ||m...@freebsd.org --- Comment #1 from Mark Johnston --- I just hit this panic with syzkaller as well. This seems like a somewhat recent regression. The panic arises in arc_state_fini(): zfs_refcount_destroy(&arc_anon->arcs_size[ARC_BUFC_DATA]); A previous zfs_refcount_destroy(&arc_anon->arcs_esize[ARC_BUFC_METADATA]); succeeded. -- You are receiving this mail because: You are the assignee for the bug.
[Bug 239604] FIONREAD ioctl returns the wrong result on a master pty after the slave has been closed
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=239604 Kyle Evans changed: What|Removed |Added URL||https://reviews.freebsd.org ||/D43457 Assignee|b...@freebsd.org|kev...@freebsd.org Status|New |In Progress CC||b...@freebsd.org, ||kev...@freebsd.org -- You are receiving this mail because: You are on the CC list for the bug. You are the assignee for the bug.
[Bug 275830] APU2 based router freezes after upgrade to 14.0-RELEASE
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=275830 --- Comment #5 from Espen --- I was able to get a freeze with the serial console attached. There was no relevant information displayed. I can share a screenshot if needed. Meanwhile I've done a few things that I thought might help, but didn't: - Disabled igmpproxy - Updated the BIOS: https://pcengines.github.io/ I also looked for similar issues on pfsense with no luck. I know a lot of those APU boards are used there and they've been on 14 for a while: 2023-12-07 14.0-CURRENT@0c783a37d5d5 via https://docs.netgate.com/pfsense/en/latest/releases/versions.html I'll run a memtest the next days and if that's all good, I'll most likely revert back to 13.x or is there anything else I can do? Best, Espen -- You are receiving this mail because: You are the assignee for the bug.
