https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=250749
--- Comment #3 from Helge Oldach ---
I suspect this behaviour is visible in other drivers as well: I am seeing the
same behaviour on a bge interface with several subinterfaces configured for
"DHCP", but only the first one triggers devd to c
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=267871
eagerpython changed:
What|Removed |Added
CC||krampusdecor...@gmail.com
--- Commen
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=273956
--- Comment #13 from Ed Maste ---
(In reply to Konstantin Belousov from comment #12)
The issue is just in Valgrind's assumptions of what the mappings will be.
I spotted this comment in its src:
/* A segment in the initial /proc/self/map
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=273962
--- Comment #8 from Rick Macklem ---
The most recent Linux man page for copy_file_range(2)
appears to be here:
https://man7.org/linux/man-pages/man2/copy_file_range.2.html
In it:
EINVAL The flags argument is not 0.
EINVAL fd
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=273953
--- Comment #3 from commit-h...@freebsd.org ---
A commit in branch main references this bug:
URL:
https://cgit.FreeBSD.org/src/commit/?id=c584bb9cac16bc200ac45cc8b709e7e7e99e24bb
commit c584bb9cac16bc200ac45cc8b709e7e7e99e24bb
Author:
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=273956
Konstantin Belousov changed:
What|Removed |Added
CC||k...@freebsd.org
--- Comment
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=273956
Ed Maste changed:
What|Removed |Added
Attachment #245082|text/x-csrc |text/plain
mime type|
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=273962
--- Comment #7 from Rick Macklem ---
Now that I have taken a quick look, doing
the shared memory fallback will be quite a
bit of work, given the range locking stuff.
Something like:
- Define a new f_op (f_copy_file_range()).
- Factor most o
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=273962
--- Comment #6 from Rick Macklem ---
It looks like there would need to be a
layering violation, since the code that
goes in kern_copy_file_range() will need
to be specific to shm_ops, since the
range lock code needs to use shm_mtx.
(Or a ne
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=273956
--- Comment #10 from Ed Maste ---
Interesting - I made a little program that uses KERN_PROC_VMMAP and dumps its
own map. When I run it normally I see the 4th PT_LOAD as swap:
$ ./a.out
1 0x0020 - 0x00201000 (0x1000
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=273962
--- Comment #5 from Rick Macklem ---
I looked and doing the fallback will
require some messing about.
shm_read() and shm_write() do
range locking however copy_file_ramge()
needs to do range locking on both
fds before copying.
I think varia
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=250749
Johan Ström changed:
What|Removed |Added
CC||jo...@stromnet.se
--- Comment #2 fro
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=273962
--- Comment #4 from Rick Macklem ---
Long ago when I first worked on 6th edition
(late 1970s) there was the "everything was
a file" philosophy. However, things like
shared emeory did not exist. The fact that
the code does not use vnodes su
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=273956
--- Comment #9 from Paul Floyd ---
And for reference, if I trigger an assert inside a Valgrind built on Alpine I
get
host stacktrace:
==10726==at 0x5804379A: show_sched_status_wrk (m_libcassert.c:407)
==10726==by 0x580438B7: report
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=273956
--- Comment #8 from Paul Floyd ---
(In reply to Ed Maste from comment #6)
I know a thing or two about this.
Initially Valgrind would only trigger reading debuginfo when it considered a
file to have finished mapping. That used to mean seei
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=273956
--- Comment #7 from Paul Floyd ---
(In reply to Ed Maste from comment #5)
Ah so the RW PT_LOAD section is starting out swapped so the sysctl doesn't see
the file.
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=273956
--- Comment #6 from Ed Maste ---
On 13.2 for /bin/sleep I see:
PID STARTEND PRT RES PRES REF SHD FLAG TP PATH
1120 0x2a57e7f66000 0x2a57e7f67000 r--12 3 1 CN--- vn
/bin/sleep
1120
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=273956
--- Comment #5 from Ed Maste ---
Ok, I can stop it there:
(lldb) b parse_procselfmaps
Breakpoint 1: where = memcheck-amd64-freebsd`parse_procselfmaps + 37 at
aspacemgr-linux.c:3926:12, address = 0x38133885
(lldb) run
Process 30476
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=273962
Dmitry Chagin changed:
What|Removed |Added
CC||dcha...@freebsd.org
--- Comment #3
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=273956
Graham Perrin changed:
What|Removed |Added
CC||grahamper...@gmail.com
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=273962
Graham Perrin changed:
What|Removed |Added
Status|New |Open
Component|kern
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=273956
--- Comment #4 from Ed Maste ---
Hi Paul, I'm using valgrind-3.21.0,1 from pkg, and a slightly older CURRENT
around the time of the stable/14 branch. I will update one or both if necessary
to reproduce, but want to know what steps I should
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=273962
--- Comment #2 from David Chisnall ---
(In reply to Rick Macklem from comment #1)
> The title uses "file" which I think of as "regular file",
On *NIX, everything is a file. I found it very surprising that it didn't work
with shared memory
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=273664
Marek Zarychta changed:
What|Removed |Added
URL||https://github.com/OpenVPN/
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=273962
--- Comment #1 from Rick Macklem ---
Yes, I think the man page needs to be patched so
that it clearly states "file descriptors for
regular file" and add the case of no-regular files
to EINVAL.
The title uses "file" which I think of as "reg
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=273956
--- Comment #3 from Paul Floyd ---
Hi Ed
Which versions of FreeBSD and Valgrind are you using?
I was running my dev buuild of Valgrind under gdb when I ran procstat.
The easiest thing is to use a dummy exe that just does a big sleep() an
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=273966
Ed Maste changed:
What|Removed |Added
Assignee|b...@freebsd.org|ema...@freebsd.org
--
You are receivin
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=273966
Ed Maste changed:
What|Removed |Added
CC||ema...@freebsd.org
--- Comment #3 from
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=273956
Ed Maste changed:
What|Removed |Added
CC||ema...@freebsd.org
--- Comment #2 from
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=273966
John Hein changed:
What|Removed |Added
Attachment #245052|0 |1
is obsolete|
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=269375
Yuri Pankov changed:
What|Removed |Added
Resolution|--- |FIXED
Status|New
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=255646
Yuri Pankov changed:
What|Removed |Added
Status|Open|Closed
Resolution|---
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=269375
--- Comment #4 from commit-h...@freebsd.org ---
A commit in branch stable/13 references this bug:
URL:
https://cgit.FreeBSD.org/src/commit/?id=a4916232acd614d4d7d7226d678b427aacb9730e
commit a4916232acd614d4d7d7226d678b427aacb9730e
Author:
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=255646
--- Comment #4 from commit-h...@freebsd.org ---
A commit in branch stable/13 references this bug:
URL:
https://cgit.FreeBSD.org/src/commit/?id=a4916232acd614d4d7d7226d678b427aacb9730e
commit a4916232acd614d4d7d7226d678b427aacb9730e
Author:
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=273966
--- Comment #1 from John Hein ---
Created attachment 245052
--> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=245052&action=edit
[patch] use non-deprecated elf_getphdrnum() rather than elf_getphnum()
--
You are receiving this mail
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=273966
John Hein changed:
What|Removed |Added
See Also||https://bugs.freebsd.org/bu
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=273966
Bug ID: 273966
Summary: libprocstat: use elf_getphdrnum() rather than
deprecated elf_getphnum()
Product: Base System
Version: CURRENT
Hardware: Any
OS
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=273962
Bug ID: 273962
Summary: copy_file_range does not work on shared memory objects
Product: Base System
Version: CURRENT
Hardware: Any
OS: Any
Status: New
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=273418
--- Comment #25 from Eugene Grosbein ---
(In reply to Eugene Grosbein from comment #23)
Also, noted virtual machine had Uptime: 1d2h59m35s when I decided to power it
down with "shutdown -p now" and it printed devfs-related LOR to its conso
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=271607
Bug 271607 depends on bug 273920, which changed state.
Bug 273920 Summary: 14.0-RELEASE release notes: flesh on the skeleton
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=273920
What|Removed |Added
---
40 matches
Mail list logo