On Thu, May 22, 2025 at 03:59:14PM +, Brooks Davis wrote:
> On Thu, May 22, 2025 at 08:04:19AM +0300, Konstantin Belousov wrote:
> > On Wed, May 21, 2025 at 11:23:12PM +, Brooks Davis wrote:
> > > On Wed, May 21, 2025 at 11:07:09AM -0600, Warner Losh wrote:
> > &
On Wed, May 21, 2025 at 11:23:12PM +, Brooks Davis wrote:
> On Wed, May 21, 2025 at 11:07:09AM -0600, Warner Losh wrote:
> > In short, I'd love to widen the interface, but there's a number of practical
> > issues in the way.
>
> I think caching something in the kernel of later retrieval or add
On Fri, May 16, 2025 at 10:38:58PM +0200, Kristof Provost wrote:
> As Lexi pointed out in another e-mail: users should assign addresses to the
> bridge, never to bridge member interfaces.
>
Could you, please, also explain why this is the requirement, besides stating
that the configuration is inv
On Fri, May 16, 2025 at 10:11:12AM -0400, Mark Johnston wrote:
> On Fri, May 16, 2025 at 03:22:52PM +0300, Andriy Gapon wrote:
> > On 27/04/2025 17:26, Mark Johnston wrote:
> > > On Thu, Apr 24, 2025 at 08:56:44AM +0300, Andriy Gapon wrote:
> > > > On 23/04/2025 21:56, Andriy Gapon wrote:
> > > > >
On Tue, May 06, 2025 at 12:49:32AM +, Ahmad Khalifa wrote:
> On Wed Apr 30, 2025 at 8:58 AM +0300, Konstantin Belousov wrote:
> > exa% pwd
> > /usr/local/x86_64-unknown-freebsd13.5/bin
> > exa% ls -l cc1 cc1plus liblto_plugin.so
> > lrwxr-xr-x 1 root wheel 60 Ap
On Wed, Apr 23, 2025 at 09:09:56PM +0300, Andriy Gapon wrote:
> On 19/04/2025 13:29, Konstantin Belousov wrote:
> > On Sat, Apr 19, 2025 at 01:25:28PM +0300, Andriy Gapon wrote:
> > > On 19/04/2025 12:39, Andriy Gapon wrote:
> > > > From a quick look at the code
On Mon, Apr 21, 2025 at 03:37:55PM -0700, Rick Macklem wrote:
> Hi,
>
> I just spotted something in the NFS server that seems like
> it is a bug, but I thought I'd check.
> (Note that I have never seen this cause a problem, but I
> think it might if a server file system is being forced
> dismounte
On Sat, Apr 19, 2025 at 01:29:15PM +0300, Konstantin Belousov wrote:
> On Sat, Apr 19, 2025 at 01:25:28PM +0300, Andriy Gapon wrote:
> > On 19/04/2025 12:39, Andriy Gapon wrote:
> > > On 19/04/2025 12:25, Andriy Gapon wrote:
> > > > On 19/04/2025 02
On Sat, Apr 19, 2025 at 01:25:28PM +0300, Andriy Gapon wrote:
> On 19/04/2025 12:39, Andriy Gapon wrote:
> > On 19/04/2025 12:25, Andriy Gapon wrote:
> > > On 19/04/2025 02:41, Konstantin Belousov wrote:
> > > > RTLD_DEEPBIND works by first iterating over all (recurs
On Sat, Apr 19, 2025 at 01:03:15AM +0300, Andriy Gapon wrote:
>
> I am trying to understand if RTLD_DEEPBIND should help in the following
> scenario or if I misunderstand its purpose.
>
> There is a program that has a parser based on lex/yacc, so there is function
> yyparse in the code and global
On Fri, Mar 21, 2025 at 02:30:40PM -0700, Mark Millard wrote:
> Under:
>
> # uname -apKU
> FreeBSD 7950X3D-ZFS 15.0-CURRENT FreeBSD 15.0-CURRENT #4
> main-n275926-a54a240c1b57-dirty: Thu Mar 13 00:44:25 PDT 2025
> root@7950X3D-ZFS:/usr/obj/BUILDs/main-ZNV4-nodbg-clang/usr/main-src/amd64.amd
On Sat, Mar 08, 2025 at 03:02:14PM -0800, Rick Macklem wrote:
> First off, I cross posted because I don't think many read freebsd-arch@.
> There seems to be a nice market for Solaris style extended attributes.
> Since ZFS is already wired for them, adding the basics is pretty
> straightforward. I a
On Tue, Feb 11, 2025 at 02:16:13AM +, Bjoern A. Zeeb wrote:
> On Tue, 11 Feb 2025, Konstantin Belousov wrote:
>
> > > __cxa_thread_call_dtors: dtr 0xe67c10 from unloaded dso, skipping
> > > ...
> >
> > Your linker is old. I believe this should cure
On Tue, Feb 11, 2025 at 12:21:29AM +, Bjoern A. Zeeb wrote:
> On Mon, 26 Jun 2023, Dimitry Andric wrote:
>
> > On 26 Jun 2023, at 17:29, Bjoern A. Zeeb
> > wrote:
> > >
> > > On Mon, 26 Jun 2023, Dimitry Andric wrote:
> > >
> > > > On 26 Jun 2023, at 17:00, Bjoern A. Zeeb
> > > > wrote:
On Thu, Jan 30, 2025 at 02:37:53AM +, Bjoern A. Zeeb wrote:
> Hi.
>
> I broke into the kernel debugger after some driver went haywire.
>
> Upon typing reset to restart the machine I got the below.
> How can we still report a LOR and panic on a lock when we
> are resetting the machine from ddb
On Wed, Jan 29, 2025 at 05:29:35AM +, jenkins-ad...@freebsd.org wrote:
> FreeBSD-main-amd64-test - Build #25976
> (4da070ce6c015a994ec4ecf3d31ee94810ea19f1) - Still unstable
>
> Build information: https://ci.FreeBSD.org/job/FreeBSD-main-amd64-test/25976/
> Full change log:
> https://ci.FreeB
On Fri, Jan 03, 2025 at 06:43:55PM -0500, Dennis Clarke wrote:
>
> I wonder if anyone else has seen such a message at shutdown :
>
>
>
> Fatal trap 12: page fault while in kernel mode
> cpuid = 0; apic id = 00
> fault virtual address = 0x0
> fault code = supervisor read data, pag
ged it to USE_TMPFS=yes, rebuilt only textproc/libsass and
> > textproc/sassc, and then after reinstalling those packages:
> >
> > $ /usr/local/bin/sassc
> > Segmentation fault
>
> And after applying Dag-Erling's patch to disable copy_file_range f
On Wed, Oct 09, 2024 at 07:34:31PM +, Paul Floyd wrote:
>
>
> On 09-10-24 08:50, Konstantin Belousov wrote:
>
> > Perhaps you can check for the presence of the symbol exit@FBSD_1.0 in the
> > backtrace to determine the situation.
>
> We don't read .gnu.ve
On Wed, Oct 09, 2024 at 06:13:44PM +, Nathan Nasby wrote:
> Hello,
>
> When I try to compile world with the latest source, I get error of
> undeclared identifiers
>
> /usr/src/usr.bin/procstat/procstat_vm.c:118:7: error: use of undeclared
> identifier ‘KVME_FLAG_SYSVSHM’
>
> 118 | KVME_FLA
On Wed, Oct 09, 2024 at 10:27:22AM +0200, Paul Floyd wrote:
> >
> > On Wed, 9 Oct 2024 at 09:08, Konstantin Belousov
> > wrote:
> >
> On Wed, Oct 09, 2024 at 06:35:08AM +, Paul Floyd wrote:
> > > The biggest problem is with Helgrind. All
On Wed, Oct 09, 2024 at 06:35:08AM +, Paul Floyd wrote:
> Hi
>
> I don't often update my 15-0-CURRENT VM. I did last week and I'm getting
> several issues.
>
> Firstly, a bit annoying, both pkg and ksh93 fail to run, giving.
> ld-elf.so.1: Shared object "libmd.so.6" not found, required by "ks
On Sun, Oct 06, 2024 at 07:56:01AM -0600, Warner Losh wrote:
> On Sun, Oct 6, 2024 at 3:09 AM Konstantin Belousov
> wrote:
>
> > On Sun, Oct 06, 2024 at 10:57:23AM +0200, Dag-Erling Smørgrav wrote:
> > > Konstantin Belousov writes:
> > > > We do not provide
On Sun, Oct 06, 2024 at 10:57:23AM +0200, Dag-Erling Smørgrav wrote:
> Konstantin Belousov writes:
> > We do not provide forward compatibility between kernel and userspace.
> > User binaries must be newer than kernel.
>
> Uh, no. The opposite, in fact.
Right, it is opp
On Sat, Oct 05, 2024 at 06:14:40PM -0700, Mark Millard wrote:
> Konstantin Belousov wrote on
> Date: Fri, 20 Sep 2024 21:09:29 UTC :
>
> > The branch main has been updated by kib:
> >
> > URL:
> > https://cgit.FreeBSD.org/src/commit/?id=2c1963d46335576d29fe21a
On Tue, Oct 01, 2024 at 11:53:33AM +0300, Konstantin Belousov wrote:
> On Tue, Oct 01, 2024 at 01:16:31PM +0700, dsdq...@hotmail.com wrote:
> > Hyper-V Gen2 VM, 8 cores, 8GB RAM. The panic is reproducible while
> > running `make -j8 buildworld`. Initially installed from
> >
On Tue, Oct 01, 2024 at 01:16:31PM +0700, dsdq...@hotmail.com wrote:
> Hyper-V Gen2 VM, 8 cores, 8GB RAM. The panic is reproducible while
> running `make -j8 buildworld`. Initially installed from
> FreeBSD-15.0-CURRENT-amd64-20240926-6a4f0c063718-272495-disc1.iso,
> updating the kernel (that I co
On Sat, Sep 21, 2024 at 04:01:29AM +0900, Yasuhiro Kimura wrote:
> From: Konstantin Belousov
> Subject: Re: eval: Pipe call failed: Cannot allocate memory
> Date: Fri, 20 Sep 2024 14:37:09 +0300
>
> > Did the poudriere run itself finished successfully?
>
> Yes,
On Fri, Sep 20, 2024 at 06:59:20PM +0900, Yasuhiro Kimura wrote:
> % uname -a
> FreeBSD rolling-vm-freebsd1.home.utahime.org 15.0-CURRENT FreeBSD
> 15.0-CURRENT #0 main-n272349-267f223f622: Fri Sep 20 17:49:44 JST 2024
> ro...@rolling-vm-freebsd1.home.utahime.org:/usr/obj/usr/src/amd64.amd64/
On Tue, Jul 30, 2024 at 10:02:37PM -0600, Warner Losh wrote:
> On Tue, Jul 30, 2024, 12:54 PM Dag-Erling Smørgrav wrote:
>
> > Miroslav Lachman <000.f...@quip.cz> writes:
> > > I'm a bit confused. If I understand it right, you say loader.conf
> > > causes less memory fragmentation, but DES said "
On Wed, Jul 24, 2024 at 01:07:39PM +, John F Carr wrote:
>
>
> > On Jul 24, 2024, at 06:50, Konstantin Belousov wrote:
> >
> > On Wed, Jul 24, 2024 at 12:34:57PM +0200, m...@freebsd.org wrote:
> >>
> >>
> >> On 24.07.2024 12:24, Konstant
On Wed, Jul 24, 2024 at 12:34:57PM +0200, m...@freebsd.org wrote:
>
>
> On 24.07.2024 12:24, Konstantin Belousov wrote:
> > On Tue, Jul 23, 2024 at 08:11:13PM +, John F Carr wrote:
> > > On Jul 23, 2024, at 13:46, Michal Meloun wrote:
> > > >
>
On Tue, Jul 23, 2024 at 08:11:13PM +, John F Carr wrote:
> On Jul 23, 2024, at 13:46, Michal Meloun wrote:
> >
> > On 23.07.2024 11:36, Konstantin Belousov wrote:
> >> On Tue, Jul 23, 2024 at 09:53:41AM +0200, Michal Meloun wrote:
> >>> The good news is
On Tue, Jul 23, 2024 at 07:46:51PM +0200, Michal Meloun wrote:
>
>
> On 23.07.2024 11:36, Konstantin Belousov wrote:
> > On Tue, Jul 23, 2024 at 09:53:41AM +0200, Michal Meloun wrote:
> > > The good news is that I'm finally able to generate a working/locking
>
On Tue, Jul 23, 2024 at 09:53:41AM +0200, Michal Meloun wrote:
> The good news is that I'm finally able to generate a working/locking
> test case. The culprit (at least for me) is if "-mcpu" is used when
> compiling libthr (e.g. indirectly injected via CPUTYPE in /etc/make.conf).
> If it is not us
[Everything and everybody in Cc: are stripped for good].
On Fri, Jul 19, 2024 at 10:38:36PM -0700, Mark Millard wrote:
> 0x201375c0 - 0x2014092c is .bss in /lib/libthr.so.3
>
> (gdb) bt
> #0 0x201aeec0 in __pthread_map_stacks_exec () from /lib/libc.so.7
> #1 0x2005d1e4 in ?? () from /libexec/ld
On Fri, Jul 12, 2024 at 10:45:31AM +, Dave Cottlehuber wrote:
> On Fri, 12 Jul 2024, at 03:39, Zhenlei Huang wrote:
> > Hi
> >
> > I observed something weird on Release 14.1.
> >
> > When rebooting my dev machine, I got
> > ...
> > IIUC all processes will get signal to quit on system reboot. Bu
On Thu, May 16, 2024 at 08:05:57PM +, Lorenzo Salvadore wrote:
> On Thursday, May 16th, 2024 at 20:26, Konstantin Belousov
> wrote:
> > > gcc13 from ports
> > > `# gcc ctors.c && ./a.out init 1 init 2 init 5 init 4 init 3 main fini 3
> > > fini 4 fin
On Thu, May 16, 2024 at 08:06:46PM +0800, Zhenlei Huang wrote:
> Hi,
>
> I'm recently working on https://reviews.freebsd.org/D45194 and got noticed
> that gcc behaves weirdly.
>
> A simple source file to demonstrate that.
>
> ```
> # cat ctors.c
>
> #include
>
> __attribute__((constructor(101
On Thu, Apr 25, 2024 at 07:49:23PM -0700, Rick Macklem wrote:
> Hi,
>
> This week I have been doing active testing as a part of an IETF
> bakeathon for NFSv4. During the week I had a NFSv4 client
> crash. On the surface, it is straightforward, in that it called
> ncl_doio_directwrite() and the fie
On Wed, Apr 24, 2024 at 01:12:39PM +0500, BSD USER wrote:
> linking kernel
> ld: error: undefined symbol: ktrcapfail
> >>> referenced by vfs_lookup.c
> >>> vfs_lookup.o:(namei)
> >>> referenced by vfs_lookup.c
> >>> vfs_lookup.o:(namei_setup)
> >>> referenced by vfs_look
On Wed, Mar 27, 2024 at 03:01:11AM +0100, Bernd Walter wrote:
> Same Problem with current:
> reeBSD 15.0-CURRENT #0 main-n268793-220ee18f1964: Thu Mar 14 02:58:39 UTC 2024
>
> real memory = 1649265344512 (1572862 MB)
> avail memory = 1057118396416 (1008146 MB)
Real memory is really the max physi
On Wed, Mar 27, 2024 at 01:00:07PM +0100, Mateusz Guzik wrote:
> Top of main, but I reproduced it on stable/14-e64d827d3 as well.
>
> Mere "timeout 2 sleep 10" correctly times out.
>
> Running "truss -f timeout 2 sleep 10" prevents timeout from killing
> sleep and the entire thing refuses to exit
can occur in some dedicated context,
like per-CPU thread, instead of userret.
>
>
> R
>
>
>
> On 3/18/24 3:42 PM, Drew Gallatin wrote:
> > No. The goal is to run on every return to userspace for every thread.
> >
> > Drew
> >
> > On Mon, M
added, and then it registers the
ast to run on next return to userspace, for the current thread.
Is it enough?
>
> Drew
>
> On Mon, Mar 18, 2024, at 2:33 PM, Konstantin Belousov wrote:
> > On Mon, Mar 18, 2024 at 07:26:10AM -0500, Mike Karels wrote:
> > > On 18 Mar 2024, at
On Mon, Mar 18, 2024 at 07:26:10AM -0500, Mike Karels wrote:
> On 18 Mar 2024, at 7:04, tue...@freebsd.org wrote:
>
> >> On 18. Mar 2024, at 12:42, Nuno Teixeira wrote:
> >>
> >> Hello all!
> >>
> >> It works just fine!
> >> System performance is OK.
> >> Using patch on main-n268841-b0aaf8beb126(
On Mon, Mar 11, 2024 at 09:03:38AM +0100, Alexander Leidinger wrote:
> Am 2024-03-10 22:57, schrieb Konstantin Belousov:
>
> > We are already low on the free bits in the flags, even after expanding
> > them
> > to 64bit. More, there are useful common fs services co
On Sun, Mar 10, 2024 at 09:50:51PM +, Kirk McKusick wrote:
> > Date: Sun, 10 Mar 2024 19:21:54 +0200
> > From: Konstantin Belousov
> > To: Kirk McKusick
> > Cc: curr...@freebsd.org
> > Subject: Re: Reason why "nocache" option is not displayed in &quo
On Sat, Mar 09, 2024 at 04:59:49PM -0800, Rick Macklem wrote:
> Hi,
>
> I would like to compare va_size to va_bytes in vn_generic_copy_file_range(),
> as a heuristic to check for a sparse file (only works for non-compressed
> file systems).
>
> The call to VOP_GETATTR(invp, ..) was replaced by vn
On Sun, Mar 10, 2024 at 01:53:05AM +, Kirk McKusick wrote:
> The issue has to do with how flags are defined in mount.h.
> Specifically there are the flags that are externally visible
> (prefixed with MNT_) and those that are for internal use
> (prefixed with MNTK_, the K standing for KERNEL). I
On Fri, Feb 23, 2024 at 08:34:21PM -0800, Gleb Smirnoff wrote:
> Hi FreeBSD/main users,
>
> the February 2024 stabilization week started with 03cc3489a02d that was tagged
> as main-stabweek-2024-Feb. At the moment of the tag creation we already knew
> about several regression caused by libc/lib
On Wed, Feb 21, 2024 at 08:20:25PM +, Brooks Davis wrote:
> That's probably worth a shot. Static linking will work anyway because
> libc.a in effect embeds libsys to retain compatability.
Please do not add libsys.so to the ABI. Right now it is an implementation
detail of libthr and libc, and
On Sat, Feb 03, 2024 at 11:10:14AM -0700, Warner Losh wrote:
> On Sat, Feb 3, 2024, 11:02 AM Konstantin Belousov
> wrote:
>
> > On Sat, Feb 03, 2024 at 11:05:10AM -0500, Daniel Eischen wrote:
> > > Will this break binary compatibility with older programs expecting those
On Sat, Feb 03, 2024 at 11:05:10AM -0500, Daniel Eischen wrote:
> Will this break binary compatibility with older programs expecting those
> symbols in libc and not linked to libsys?
As was mentioned, libc filters libsys. This means that libc exports all
the same symbols as before, but forward t
On Sat, Feb 03, 2024 at 12:12:35PM +0100, Mateusz Guzik wrote:
> On 2/3/24, David Chisnall wrote:
> > On 3 Feb 2024, at 09:15, Mateusz Guzik wrote:
> >>
> >> Binary startup is very slow, for example execve of a hello world
> >> binary in a Linux-based chroot on FreeBSD is faster by a factor of 2
On Fri, Feb 02, 2024 at 12:07:35PM -0800, Steve Kargl wrote:
> On Sun, Jan 28, 2024 at 12:04:48PM +0200, Konstantin Belousov wrote:
> > On Sat, Jan 27, 2024 at 09:22:59PM -0800, Steve Kargl wrote:
> > > On Sat, Jan 27, 2024 at 10:29:34PM +0100, Dimitry Andric wrote:
> > &
On Sat, Jan 27, 2024 at 09:22:59PM -0800, Steve Kargl wrote:
> On Sat, Jan 27, 2024 at 10:29:34PM +0100, Dimitry Andric wrote:
> > On 27 Jan 2024, at 18:08, Steve Kargl
> > wrote:
> > >
> > > In an attempt to cleanup a bit of src/lib/msun, I ran into
> > > a small issue that I cannot explain at
On Fri, Dec 29, 2023 at 01:50:34PM +0100, Dimitry Andric wrote:
> The problem is really that our kernel headers (those under sys/) require C99.
> The only thing that
> https://cgit.freebsd.org/src/commit/?id=a8b70cf26030d68631200619bd1b0ad35b34b6b8
> did was move two static inline functions from
On Fri, Dec 22, 2023 at 11:18:23PM -0800, Xin Li wrote:
> Hi,
>
> Inspired by D42961, I propose that we move forward with disabling the
> compression by default in newsyslog, as implemented in
> https://reviews.freebsd.org/D43169
>
> Historically, newsyslog has compressed rotated log files to sav
On Fri, Dec 22, 2023 at 02:03:56PM -0700, Warner Losh wrote:
> Yes. I'd prefer to make this more parameterized, maybe with sanity checks.
>
> That is, there'd be a tool that would do the right thing, based on what you
> tell it to do. we'd set the defaults to be a default install. If you want
> so
On Fri, Dec 22, 2023 at 11:36:24AM +0200, Toomas Soome wrote:
>
>
> > On 22. Dec 2023, at 11:09, Mark Millard wrote:
> >
> > Tomoaki AOKI wrote on
> > Date: Thu, 21 Dec 2023 23:21:00 UTC :
> >
> >> On Thu, 21 Dec 2023 14:22:14 +0100
> >> Dimitry Andric wrote:
> >>
> >>> Yeah, my procedure i
On Tue, Nov 14, 2023 at 01:30:25PM -0800, Rick Macklem wrote:
> On Tue, Nov 14, 2023 at 1:20 PM Konstantin Belousov
> wrote:
> >
> > On Tue, Nov 14, 2023 at 06:47:46PM +0100, Mateusz Guzik wrote:
> > > On 11/14/23, Alexander Motin wrote:
> > > > O
On Tue, Nov 14, 2023 at 07:51:39PM +0100, Mateusz Guzik wrote:
> On 11/14/23, Alexander Motin wrote:
> > On 14.11.2023 12:44, Alexander Motin wrote:
> >> On 14.11.2023 12:39, Mateusz Guzik wrote:
> >>> One of the vnodes is probably not zfs, I suspect this will do it
> >>> (untested):
> >>>
> >>> d
On Tue, Nov 14, 2023 at 06:47:46PM +0100, Mateusz Guzik wrote:
> On 11/14/23, Alexander Motin wrote:
> > On 14.11.2023 12:39, Mateusz Guzik wrote:
> >> One of the vnodes is probably not zfs, I suspect this will do it
> >> (untested):
> >>
> >> diff --git a/sys/contrib/openzfs/module/os/freebsd/zfs
On Sun, Nov 12, 2023 at 11:51:40AM -0500, Alexander Motin wrote:
> Hi Ronald,
>
> As I can see, the clone request to ZFS came through nullfs, and it crashed
> immediately on enter. I've never been a VFS layer expert, but to me it may
> be a nullfs problem, not zfs. Is there chance you was (un-)m
On Wed, Oct 25, 2023 at 07:58:41AM +, Marcin Cieslak wrote:
> Hello,
>
> is there any documentation for cdevsw methods?
> I am interested in knowing how d_map_single should
> be written.
>
> Most specifically, I want to know if the driver
> has a chance to track mmaped allocations on its own
On Mon, Sep 18, 2023 at 01:27:55PM -0500, Mike Karels wrote:
> On 18 Sep 2023, at 10:38, Michael Butler wrote:
>
> > On 8/8/23 13:50, Michael Butler wrote:
> >> On 8/8/23 10:56, Tomoaki AOKI wrote:
> >>> On Tue, 8 Aug 2023 17:02:32 +0300
> >>> Kons
On Mon, Aug 21, 2023 at 08:19:28AM +0200, Alexander Leidinger wrote:
> Am 2023-08-20 23:17, schrieb Konstantin Belousov:
> > On Sun, Aug 20, 2023 at 11:07:08PM +0200, Mateusz Guzik wrote:
> > > On 8/20/23, Alexander Leidinger wrote:
> > > > Am 2023-08-20 22:02, schr
On Sun, Aug 20, 2023 at 11:07:08PM +0200, Mateusz Guzik wrote:
> On 8/20/23, Alexander Leidinger wrote:
> > Am 2023-08-20 22:02, schrieb Mateusz Guzik:
> >> On 8/20/23, Alexander Leidinger wrote:
> >>> Am 2023-08-20 19:10, schrieb Mateusz Guzik:
> On 8/18/23, Alexander Leidinger wrote:
> >>
On Tue, Aug 08, 2023 at 10:46:12PM +0900, Tomoaki AOKI wrote:
> On Tue, 8 Aug 2023 15:38:46 +0300
> Konstantin Belousov wrote:
>
> > On Tue, Aug 08, 2023 at 06:37:35AM +0900, Tomoaki AOKI wrote:
> > > On Sun, 6 Aug 2023 12:55:07 +0300
> > > Konstantin Belousov
On Tue, Aug 08, 2023 at 06:37:35AM +0900, Tomoaki AOKI wrote:
> On Sun, 6 Aug 2023 12:55:07 +0300
> Konstantin Belousov wrote:
>
> > On Sun, Aug 06, 2023 at 06:12:38PM +0900, Tomoaki AOKI wrote:
> > > On Wed, 23 Feb 2022 01:30:28 +0200
> > > Konstantin Belousov
On Sun, Aug 06, 2023 at 06:12:38PM +0900, Tomoaki AOKI wrote:
> On Wed, 23 Feb 2022 01:30:28 +0200
> Konstantin Belousov wrote:
>
> > On Tue, Feb 22, 2022 at 06:23:17PM -0500, Alexander Motin wrote:
> > > On 22.02.2022 17:46, Konstantin Belousov wrote:
> > > >
On Tue, Aug 01, 2023 at 04:33:16PM -0700, Rick Macklem wrote:
> On Mon, Jul 31, 2023 at 11:33 PM David Chisnall wrote:
> >
> > Hi,
> >
> > This bit of the C spec is a bit of a mess. There was, I believe, a desire
> > to return volatile to its original use and make any use of volatile other
> > t
On Mon, Jul 10, 2023 at 09:39:35AM +, John F Carr wrote:
>
>
> > On Jul 9, 2023, at 19:59, Konstantin Belousov wrote:
> >
> > On Sun, Jul 09, 2023 at 11:36:03PM +, John F Carr wrote:
> >>
> >>
> >>> On Jul 9, 2023, at 19:25, K
On Sun, Jul 09, 2023 at 11:36:03PM +, John F Carr wrote:
>
>
> > On Jul 9, 2023, at 19:25, Konstantin Belousov wrote:
> >
> > On Sun, Jul 09, 2023 at 10:41:27PM +, John F Carr wrote:
> >> Kernel and system at a146207d66f320ed239c1059de9df854b66b55b7
On Sun, Jul 09, 2023 at 10:41:27PM +, John F Carr wrote:
> Kernel and system at a146207d66f320ed239c1059de9df854b66b55b7 plus some
> irrelevant local changes, four 64 bit ARM processors, make.conf sets
> CPUTYPE?=cortex-a57.
>
> I typed ^C while /bin/sh was starting a pipeline and my shell g
On Sat, May 20, 2023 at 11:38:14AM -0700, Rick Macklem wrote:
> Hi,
>
> So I did an MFC that broke the stable/13 build (it's reverted now).
> I didn't realize that changes inside _KERNEL in mount.h would do
> this, but now I know.
>
> Since it is only an issue for stable/13 (and not main), I'd li
On Wed, Apr 26, 2023 at 01:38:32PM +0200, Hans Petter Selasky wrote:
> On 4/26/23 13:12, Konstantin Belousov wrote:
> > No, in-kernel linker does not behave this way.
> > Modules need to contain explicit reference to all modules they depend upon,
> > using the MODULE_DEPEND()
On Wed, Apr 26, 2023 at 12:55:02PM +0200, Hans Petter Selasky wrote:
> On 4/26/23 12:36, Zhenlei Huang wrote:
> > Hi,
> >
> > I'm recently working on https://reviews.freebsd.org/D39638 (sysctl(9):
> > Enable vnet sysctl variables be loader tunable),
> > the changes to `sys/kern/link_elf_obj.c` ar
On Fri, Mar 31, 2023 at 01:27:54PM -0400, Ed Maste wrote:
> On Fri, 31 Mar 2023 at 12:38, Charlie Li wrote:
> >
> > Konstantin Belousov wrote:
> > > The branch main has been updated by kib:
> > >
> > > URL:
> > > https://cgit.FreeBSD.org/src/
On Mon, Feb 06, 2023 at 06:59:59PM -0700, Alan Somers wrote:
> On Mon, Feb 6, 2023 at 6:23 PM Rick Macklem wrote:
> >
> > PR#269328 reports an issue related to fspacectl() being
> > mixed with mmap'd I/O.
> >
> > When working on a fix for this for the NFS client, I realized that
> > "man fspacectl
On Tue, Jan 03, 2023 at 11:38:55AM +0100, Floyd, Paul wrote:
>
> On 30/12/2022 01:54, Konstantin Belousov wrote:
> >
> > The backtrace is needed to make a further analysis.
>
>
> Any suggestions for getting a backtrace? I get the panic booting either the
> insta
On Tue, Jan 03, 2023 at 08:20:16AM +, Chen, Alvin W wrote:
> >
> > [EXTERNAL EMAIL]
> >
> > On 2022-11-14 09:09 +0200, Konstantin Belousov wrote:
> > >
> > > You might use this patch meantime
> > > https://urldefense.com/v3/__https://kib
On Thu, Dec 29, 2022 at 09:39:44AM +0100, Paul Floyd wrote:
>
>
> On 28-12-22 18:12, Ronald Klop wrote:
>
> >
> > I've had success to capture errors by recording the screen with my phone
> > and playing back on slow speed.
> > Another option might be to enable serial port for the console of the
On Fri, Dec 23, 2022 at 03:47:33PM -0800, Mark Millard wrote:
> Jonathan Chen wrote on
> Date: Fri, 23 Dec 2022 18:40:27 UTC :
>
> > On 24/12/22 07:14, Mark Millard wrote:
> > > Jonathan Chen wrote on
> > > Date: Thu, 22 Dec 2022 19:21:37 UTC :
> > >
> > >> I recently updated my package builder
der Lake/Raptor Lake)
> > support
> >
> >
> > [EXTERNAL EMAIL]
> >
> > On 2022-11-14 09:09 +0200, Konstantin Belousov wrote:
> > >
> > > You might use this patch meantime
> > > https://urldefense.com/v3/__https://kib.kiev.ua/git/gitw
On Mon, Nov 14, 2022 at 06:50:20AM +, Chen, Alvin W wrote:
>
>
> Internal Use - Confidential
>
>
> > -Original Message-
> > From: Mike Karels
> > Sent: 2022年10月27日 23:17
> > To: Chen, Alvin W
> > Cc: freebsd-current
> > Subject: Re: Status of Intel Hybrid CPU support (Alder Lake/Ra
On Tue, Sep 06, 2022 at 10:36:52AM -0600, Alan Somers wrote:
> On Tue, Sep 6, 2022 at 9:07 AM Warner Losh wrote:
> >
> >
> >
> > On Tue, Sep 6, 2022 at 7:34 AM Konstantin Belousov
> > wrote:
> >>
> >> On Mon, Sep 05, 2022 at 08:41:58AM -0600,
On Mon, Sep 05, 2022 at 08:41:58AM -0600, Alan Somers wrote:
> On Sat, Sep 3, 2022 at 11:10 PM Konstantin Belousov
> wrote:
> >
> > On Sat, Sep 03, 2022 at 10:19:12AM -0600, Alan Somers wrote:
> > > Our /usr/include headers define a lot of symbols that are used by
>
On Sat, Sep 03, 2022 at 10:19:12AM -0600, Alan Somers wrote:
> Our /usr/include headers define a lot of symbols that are used by
> critical utilities in the base system like ps and ifconfig, but aren't
> stable across major releases. Since they aren't stable, utilities
> built for older releases w
On Fri, Sep 02, 2022 at 04:11:40PM +0200, Mateusz Guzik wrote:
> On 9/2/22, Konstantin Belousov wrote:
> > On Fri, Sep 02, 2022 at 02:05:37PM +0200, Mateusz Guzik wrote:
> >> Is this really of practical use today?
> >>
> >> I have a WIP patch which needs t
On Fri, Sep 02, 2022 at 02:05:37PM +0200, Mateusz Guzik wrote:
> Is this really of practical use today?
>
> I have a WIP patch which needs to temporarily store something on the
> stack and should things go wrong enough it will be accessed by UMA,
> which can't handle the fault nor decide to skip t
On Mon, Aug 22, 2022 at 02:56:47PM +, Bjoern A. Zeeb wrote:
> Hi,
>
> I am trying to get some arm64 up and running a bit but cannot use
> loader. I have an MD_ROOT embedded in the kernel with /rescue on it.
> I set INIT_PATH=/rescue/sh .
>
> However that doesn't seem to work:
>
> start_init:
On Fri, May 13, 2022 at 01:16:39PM +0200, obiwac wrote:
> Wassup,
>
> This may not be strictly speaking a bug with rtld, but it sure is
> weird/awkward behaviour considering the existing information I could
> gather.
>
> In an unversioned shared object which references a symbol which has
> multip
On Wed, Feb 23, 2022 at 12:25:24PM -0500, Alexander Motin wrote:
> On 22.02.2022 19:00, Konstantin Belousov wrote:
> > On Tue, Feb 22, 2022 at 06:53:09PM -0500, Alexander Motin wrote:
> > > On 22.02.2022 18:41, Konstantin Belousov wrote:
> > > > On Tue, Feb 22, 2022
On Tue, Feb 22, 2022 at 06:23:17PM -0500, Alexander Motin wrote:
> On 22.02.2022 17:46, Konstantin Belousov wrote:
> > Ok, the next step is to get the CPU feature reports from P- vs. E- cores.
> > Patch below should work, with verbose boot.
>
> Not much difference on that
On Sat, Feb 19, 2022 at 07:26:24PM -0500, Alexander Motin wrote:
> On 19.02.2022 13:23, Konstantin Belousov wrote:
> > On Sat, Feb 19, 2022 at 12:14:16PM -0500, Alexander Motin wrote:
> > > On 19.02.2022 12:02, Mike Karels wrote:
> > > > On 18 Feb 2022, at 20:55, Tomo
On Sat, Feb 19, 2022 at 12:14:16PM -0500, Alexander Motin wrote:
> On 19.02.2022 12:02, Mike Karels wrote:
> > On 18 Feb 2022, at 20:55, Tomoaki AOKI wrote:
> > > Just a thought, but can it be the reason with timing (e.g., rendezvous
> > > within (i)threads, hardware controlls without using hardwar
On Thu, Feb 03, 2022 at 11:52:48AM +0100, Jesper Schmitz Mouridsen wrote:
> Hi
> d950c5898a2d8733cd6e75e7ef82b08acac79b34 breaks arm64 with options IOMMU.
Which kernel config is it? Or is it your custom config?
If the later, please provide it to me.
>
> grep -nir vm_page.h sys/arm64/iommu/iommu_
On Tue, Jan 04, 2022 at 09:07:47AM +0900, Tomoaki AOKI wrote:
> I myself never used NFS, but I don't think it a POLA violation,
> because...
> *Keeping latest-stable (formerly, v3?) to oldest (v2) order.
>
> *Usually, once new version is considered stable, security fixes
>are first done on
1 - 100 of 1265 matches
Mail list logo
