https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=261457
--- Comment #1 from Yuri ---
It's mld_domifattach(), right? And NULL check is "if (mli == NULL)".
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=261458
Bug ID: 261458
Summary: Fix a possible Null pointer dereference in
igmp_domifattach()
Product: Base System
Version: Unspecified
Hardware: Any
OS: Any
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=261457
Bug ID: 261457
Summary: Fix a possible Null pointer dereference in
mld_is_addr_reported()
Product: Base System
Version: Unspecified
Hardware: Any
OS:
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=261455
Bug ID: 261455
Summary: Fix a possible Null pointer dereference in
svc_dg_create()
Product: Base System
Version: Unspecified
Hardware: Any
OS: Any
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=261454
Bug ID: 261454
Summary: Fix a possible Null pointer dereference about
svc_xprt_alloc()
Product: Base System
Version: Unspecified
Hardware: Any
OS: Any
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=261434
Alan Somers changed:
What|Removed |Added
Resolution|FIXED |Works As Intended
--- Comment #19 fr
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=261453
--- Comment #1 from Zhou Qingyang ---
Created attachment 231293
--> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=231293&action=edit
A simple fix for this bug
--
You are receiving this mail because:
You are the assignee for the bu
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=261453
Bug ID: 261453
Summary: Fix a possible Null pointer dereference in
ocs_hw_get_profile_list_cb()
Product: Base System
Version: Unspecified
Hardware: Any
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=261434
Ivan Rozhuk changed:
What|Removed |Added
Resolution|Works As Intended |FIXED
--- Comment #18 from Ivan Rozh
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=261434
Alan Somers changed:
What|Removed |Added
Status|New |Closed
Resolution|---
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=261434
Ivan Rozhuk changed:
What|Removed |Added
Resolution|Works As Intended |---
Status|Closed
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=244470
--- Comment #22 from lb...@disroot.org ---
(In reply to Kirk McKusick from comment #21)
Thanks.
The comment is very informative.
I'm going to try the advice.
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=261434
Alan Somers changed:
What|Removed |Added
Resolution|FIXED |Works As Intended
--
You are receiv
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=261434
--- Comment #15 from Alan Somers ---
(In reply to Ivan Rozhuk from comment #14)
> 1. https://github.com/libfuse/libfuse
> blob/b08e275083d0316fa4d735d457869d62ce4114de/lib/fuse.c#L2877
> At least here atime+mtime required together.
That's
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=261434
Ivan Rozhuk changed:
What|Removed |Added
Resolution|Works As Intended |FIXED
--- Comment #14 from Ivan Rozh
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=261434
Alan Somers changed:
What|Removed |Added
Summary|[fusefs] mtime and ctime|[sysutils/fusefs-sshfs]
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=261434
Alan Somers changed:
What|Removed |Added
Resolution|--- |Works As Intended
Status
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=261434
--- Comment #12 from Ivan Rozhuk ---
(In reply to Alan Somers from comment #11)
> Looking at the code you sent, sshfs_utimens is ignoring the tv_nsec field,
> which is clearly a bug.
I agree that libfuse+sshfs code is not clean, but sshf
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=244470
--- Comment #21 from Kirk McKusick ---
(In reply to lbfoo from comment #20)
This bug has been fixed in 13-STABLE but has not been issued as an errata.
Unless an errata is issued for it, it will not appear in a FreeBSD13.0-RELEASE.
Rather yo
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=261434
--- Comment #11 from Alan Somers ---
(In reply to Ivan Rozhuk from comment #10)
Always sending mtime along with atime would be exactly the wrong thing for the
kernel to do. Only sending atime is what it's supposed to do.
Looking at the co
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=261434
--- Comment #10 from Ivan Rozhuk ---
(In reply to Alan Somers from comment #9)
> All the kernel does it send upcalls like FUSE_SETATTR to the fuse server
It come here:
https://github.com/libfuse/libfuse/blob/b08e275083d0316fa4d735d457869d
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=261434
--- Comment #9 from Alan Somers ---
(In reply to Ivan Rozhuk from comment #8)
What is utimens? FreeBSD has no such thing. Do you mean utimensat? utimensat
is a syscall. The kernel can't call it. All the kernel does it send upcalls
like
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=261434
--- Comment #8 from Ivan Rozhuk ---
(In reply to Alan Somers from comment #7)
> The FUSE_SETATTR command allows the kernel to set any combination of
> timestamps
It may allow whatever, but it call utimens() with limited interface.
Even m
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=261448
Bug ID: 261448
Summary: ZFS VOP_RECLAIM causes long stalls during package
builds
Product: Base System
Version: CURRENT
Hardware: Any
OS: Any
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=261434
--- Comment #7 from Alan Somers ---
I meant, "the kernel only tries to change the file's atime". Sorry for the
typo. The FUSE_SETATTR command allows the kernel to set any combination of
timestamps, or none. For example, here is the debug
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=261446
Bug ID: 261446
Summary: freebsd-update should not create boot environment when
it's not making changes to the boot environment
Product: Base System
Version: CURRENT
H
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=261434
--- Comment #6 from Ivan Rozhuk ---
(In reply to Alan Somers from comment #5)
> The kernel only tries to change the file's mtime.
_M_time?
> I think this must be a bug in sshfs. Have you tried reporting it upstream?
No, I do not try t
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=261434
--- Comment #5 from Alan Somers ---
I can reproduce the problem with sshfs, but not with fuse-ext2 or bfffs. The
kernel only tries to change the file's mtime. I think this must be a bug in
sshfs. Have you tried reporting it upstream?
--
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=261434
--- Comment #4 from Ivan Rozhuk ---
That debug show that on file opened as RO some attributes changed before close.
root@rimwks:~# ls /home/rim/mnt/tmp/root/minipro/dist.sh
-rwxr-xr-x 1 root wheel 748B Jan 24 23:45:46 2022
/home/rim/mn
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=261434
--- Comment #3 from Alan Somers ---
Are you sure that mtime is changing? The debug traffic you pasted below
doesn't show that. Please show the output of "stat -x SOME_FILE" before and
after "cat". It might be interesting to check its out
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=261434
--- Comment #2 from Ivan Rozhuk ---
(In reply to Alan Somers from comment #1)
atime changed with mtime and ctime - this is bug.
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=261434
Ivan Rozhuk changed:
What|Removed |Added
Summary|[fusefs] change mtime and |[fusefs] mtime and ctime
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=260955
Stefan B. changed:
What|Removed |Added
Resolution|--- |FIXED
Status|New
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=261441
Bug ID: 261441
Summary: bsdinstall installs ports tree incorrectly
Product: Base System
Version: Unspecified
Hardware: Any
OS: Any
Status: New
Sever
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=261440
Bug ID: 261440
Summary: vt newcons breaks suspend/resume for all graphics
cards that do not use KMS drivers
Product: Base System
Version: Unspecified
Hardware: Any
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=261439
Bug ID: 261439
Summary: vt newcons switches to graphics mode ignoring
hw.vga.textmode="YES" setting
Product: Base System
Version: Unspecified
Hardware: Any
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=261438
Wolfram Schneider changed:
What|Removed |Added
Assignee|b...@freebsd.org|wo...@freebsd.org
--
You are
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=261438
Wolfram Schneider changed:
What|Removed |Added
URL||https://reviews.freebsd.org
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=261311
--- Comment #3 from Stefan B. ---
Sorry for late reply.
I added the section below to the kernel configuration file and
it definitely has no effect at all.
I have tested this (and other things) on several different computers with many
diff
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=261438
Bug ID: 261438
Summary: mktemp(1): better unique file names
Product: Base System
Version: CURRENT
Hardware: Any
OS: Any
Status: New
Severity: Affect
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=261437
Bug ID: 261437
Summary: outdated mktemp(1) examples
Product: Documentation
Version: Latest
Hardware: Any
OS: Any
Status: New
Severity: Affects Many
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=261434
--- Comment #1 from Alan Somers ---
Please update the bug title to clarify if "change mtime and ctime on every read
file" is what you WANT to happen, or what is happening but SHOULDN'T be. I
think you're describing the intended behavior of
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=261434
Bug ID: 261434
Summary: [fusefs] change mtime and ctime on every read file
Product: Base System
Version: 13.0-STABLE
Hardware: Any
OS: Any
Status: New
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=207431
VVD changed:
What|Removed |Added
CC||v...@unislabs.com
--- Comment #8 from VVD -
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=261431
Bug ID: 261431
Summary: FreeBSD 13-RELEASE April 2021 , boot on CPU Intel CPX
6348H goes to kernel trap.
Product: Base System
Version: 13.0-RELEASE
Hardware: Any
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=261200
--- Comment #9 from Fernando Apesteguía ---
Thanks for the explanation Jills!
Would you consider adding the modification to the man page? I am not an src
committer or a member of manpages.
Cheers.
--
You are receiving this mail because:
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=228555
Robert Wing changed:
What|Removed |Added
Status|New |Closed
CC|
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=57018
Robert Wing changed:
What|Removed |Added
CC||r...@freebsd.org
Status|O
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=136945
Robert Wing changed:
What|Removed |Added
Status|Open|Closed
CC|
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=73019
Robert Wing changed:
What|Removed |Added
Resolution|--- |Feedback Timeout
CC|
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=132331
Robert Wing changed:
What|Removed |Added
Status|Open|Closed
Resolution|---
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=136968
Robert Wing changed:
What|Removed |Added
Status|Open|Closed
CC|
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=129231
Robert Wing changed:
What|Removed |Added
Resolution|--- |Overcome By Events
C
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=135469
Robert Wing changed:
What|Removed |Added
Status|Open|Closed
CC|
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=138002
Robert Wing changed:
What|Removed |Added
Resolution|--- |Overcome By Events
C
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=94849
Robert Wing changed:
What|Removed |Added
Resolution|--- |Overcome By Events
Status
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=244470
lb...@disroot.org changed:
What|Removed |Added
CC||lb...@disroot.org
--- Comment #
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=260116
--- Comment #2 from Björn Svensson ---
After some investigations we have seen that the introduction of
"sendfile(2) system call' required some changes in the struct sockbuf.
The field sb_cc was split into sb_ccc and sb_acc in commit: 0f9d0a
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=232657
Mateusz Kwiatkowski changed:
What|Removed |Added
Status|Open|Closed
Resolution|--
59 matches
Mail list logo