Date:Tue, 28 May 2024 22:46:09 -0400 (EDT)
From:Mouse
Message-ID: <202405290246.waa17...@stone.rodents-montreal.org>
| I question whether it actually works except by accident; see RFC 6093.
I hadn't seen that one before, I stopped seriously following the IETF
Date:Tue, 28 May 2024 11:03:02 +0200
From:Johnny Billquist
Message-ID: <3853e930-4e77-4f6d-8a73-ec826a067...@softjar.se>
| This is a bit offtopic, but anyway...
So it is, but anyway...
[Quoting Mouse:]
| > TCP's urgent pointer is well defined. It is not,
Date:Fri, 26 Jan 2024 09:26:38 - (UTC)
From:mlel...@serpens.de (Michael van Elst)
Message-ID:
| Fortunately the drive geometry isn't really used anywhere. All
| accesses just use the logical block addresses.
I have been meaning to suggest for ages that we
If you are able, try building a kernel with the patch below.
I suspect this should probably apply without too many problems
to any reasonably modern NetBSD kernel version, patch is to
src/sys/dev/scsipi/sd.c
If patch(1) won't just work on your kernel sources, just
edit that fike, search for
Date:Sun, 24 Dec 2023 13:49:53 +0100
From:Johnny Billquist
Message-ID:
| In my opinion, all of these POSIX calls that take a time argument should
| really have been done the same as clock_gettime(), in that you specify
| what clock it should be based on.
Date:Tue, 10 Oct 2023 12:42:48 +0100
From:David Brownlee
Message-ID:
| I have a system which records the output of "sysctl -n kern.boottime"
| as part of a dhcpcd-exit.hook to ensure some processing only occurs
| once per boot.
Cron's @reboot might help with
Date:Sun, 17 Sep 2023 20:07:39 +
From:"Greg Oster"
Message-ID: <20230917200739.b9dadf...@cvs.netbsd.org>
| Implement hot removal of spares and components. From manu@.
|
| Implement a long desired feature of automatically incorporating
| a used spare into
Date:Mon, 25 Sep 2023 09:45:25 - (UTC)
From:mlel...@serpens.de (Michael van Elst)
Message-ID:
| There can be multiple EFI system partitions on a drive,
That was my understanding from reading the spec.
| but it sometimes confuses software,
What can I say to
Date:Mon, 25 Sep 2023 05:57:49 +
From:Emmanuel Dreyfus
Message-ID:
| bootme.cfg is searched in EFI paririon /EFI/NetBSD/boot.cfg
Which EFI partition? I think I have about 5 or 6, sprinkled around
various bootable devices (more than one on some). None of
Date:Sun, 24 Sep 2023 17:41:30 +
From:Taylor R Campbell
Message-ID: <20230924174130.481dd60...@jupiter.mumble.net>
| Why would bootme be usually set on the EFI system partition?
|
| The documentation in gpt(8) needs to be clarified -- and I'm not sure
|
Date:Mon, 18 Sep 2023 19:21:09 +0200
From:Martin Husemann
Message-ID: <20230918172109.ga4...@mail.duskware.de>
| A fallback similar to the current implementation picking the first non-swap
| partition would be usefull.
The first netbsd style partition (not just
Date:Sat, 16 Sep 2023 05:01:00 +
From:Emmanuel Dreyfus
Message-ID:
| Initial proposal was to aad access to the bootme flag in dkwedge,
| which has been considered bad design, and I agreed with that.
Yes, but that's not what was really wrong with the
Date:Fri, 15 Sep 2023 22:46:47 +
From:Emmanuel Dreyfus
Message-ID:
| You noted that latest patch does not introduce bootme stuff
| into dkwaedge code, right?
I didn't attempt to read the patch, no. Just the regular text
parts of the mail thread.
kre
Date:Tue, 12 Sep 2023 07:21:10 +
From:Emmanuel Dreyfus
Message-ID:
| Context: if a RAIDframe set contains a GPT, it does not honour the
| bootme atrtribute when loking for the root partition. The current
| behavior hardcodes the use of the first
Date:Fri, 15 Sep 2023 15:15:10 +
From:Emmanuel Dreyfus
Message-ID:
| Ths user took care of setting bootme so that botstrap finds
| the kernel, and we should disregard this explicit setting
| when mounting root?
I agree with others, where you boot from
I agree with some of what you are proposing, but disagree with much
of it.
Certainly simplifying our header file mess is important, but that's
not going to happen overnight. One particular example of that below.
And using opaque etruct definitions where possible, rather than
void * in
I'm dual-posting this to tech-kern and tech-userlevel, as while it is
a userlevel issue, it could have kernel implications. Please respect
the Reply-To and send replies only to tech-userlevel
You may have noticed that a recent change (mine) to the pathadj()
function (which converts an abritrary
Date:Sun, 30 Apr 2023 05:25:41 +
From:David Holland
Message-ID:
| Close-on-fork is apparently either coming or already here, not sure
| which, but it's also per-descriptor.
We don't have it, but it will be in Posix-8. Largely inspired by the
needs of
Date:Sun, 19 Mar 2023 07:05:52 +
From:David Holland
Message-ID:
| "They're per-open"
That's not bad for this level of description.
| ...which is not actually difficult to understand since it's the same
| as the seek pointer behavior; that is, seek
Date:Sat, 18 Mar 2023 19:46:17 -0400 (EDT)
From:Mouse
Message-ID: <202303182346.taa01...@stone.rodents-montreal.org>
| Except they aren't. They're on open file table entries, something
| remarkably difficult to describe in a way that doesn't just refer to
|
Date:Sat, 18 Mar 2023 11:32:37 -0400 (EDT)
From:Mouse
Message-ID: <202303181532.laa29...@stone.rodents-montreal.org>
| On examination, the manpages available to me (including the one at
| http://man.netbsd.org/flock.2) turn out to say nothing to clarify this.
Date:Thu, 9 Mar 2023 16:21:53 +0900
From:Masanobu SAITOH
Message-ID: <38ae66bd-1b37-c0ef-5a43-52e0c0a2a...@execsw.org>
| Alder Lake-N? 4 E-cores share one microcode image. I have i7-12700 and it
| has 4 E-cores. Those 4 cores share one microcode image.
Mine is
Date:Fri, 3 Mar 2023 21:46:22 -0800
From:"William 'Cryo' Coldwell"
Message-ID: <7ce92f54-3746-4106-bd63-16e5e4cbc...@netbsd.org>
| To throw some extra fun mixture into this discussion: As of 5.19
| Linux will no longer allow late microcode loading:
|
| ref:
Date:Fri, 03 Mar 2023 14:04:39 +1100
From:matthew green
Message-ID: <12620.1677812...@splode.eterna.com.au>
| duh. this is user error.
Oh. Double duh... "Me too".
kre
And a correction, I missed uses of -v in arch/* where it seems to apply
only to output from "cpuctl identify", and mostly on aarch64 processors
(seems to be very little change on x86, and no changes at all elsewhere,
arm (32) sparc sparc64, and definitely nothing on anything else).
kre
Date:Fri, 03 Mar 2023 09:25:29 +1100
From:matthew green
Message-ID: <14071.1677795...@splode.eterna.com.au>
| we should do this as well, it should fairly simple. we already
| display the relevant info in "cpuctl identify 0" eg:
Yes, identify shows all of the
This message is about a proposed userland modification, but it seems
more kernelish to me, hence I am asking here on tech-kern, rather than
on tech-userlevel
When my system boots (intel cpu) it runs the intel-microcode (from pkgsrc)
microcode update.
Since it is an Intel cpu, that means running
Date:Wed, 1 Mar 2023 12:44:08 -0600
From:Qingyao Sun
Message-ID: <53774732-c592-43f5-af0f-8a1f6bb03...@icloud.com>
| Also I am using the @icloud address hereafter as per kreâs preference.
It is not so much preference, as that you simply would never receive a
I like this idea a lot more than the inetd/rc.d idea. I am not sure that
"Improvements on Lua Support" is a good title, unless you're actually planning
on working on the kernel Lua implementation, and it doesn't sound like that.
I'd suggest something more like "Using Lua scripts to improve
Date:Sun, 22 Jan 2023 20:27:24 +0100
From:tlaro...@polynum.com
Message-ID:
| +Zone kernel: Available graphics memory: 9007199254079374 KiB
I see something like that too, but while it is obviously absurd,
I'm not sure that it actually does any harm (maybe) - my
POSIX is finally removing the inane requirement that all of the
standard utilities built into the shell (except for the special
builtin utilities - those are ones like break : set ...) be also
implemented as file system commands.
We have never bothered with that requirement, and have consistently
Date:Sun, 23 Oct 2022 09:50:20 +
From:Taylor R Campbell
Message-ID: <20221023095027.eb8ef60...@jupiter.mumble.net>
| I wasn't able to find a clear statement of the semantics anywhere:
| Is it keyed by (dev,ino), by pathname, by some kind of normalized
|
This isn't really a tech-kern question, but never mind.
You shouldn't need wedges at all, and I'd advise against trying
to force them to work (it is probably possible, but far more work
than you need to do).
Go back to your original kernel, and when that's running, do
disklabel wd0
On
Date:Fri, 23 Sep 2022 22:57:52 -0400
From:"David H. Gutteridge"
Message-ID:
| Sometimes it's necessary to test for when a feature was added in a
| -current release, and there's no simple or precise way to do it, as
| you've noted. If a feature was added
Date:Wed, 21 Sep 2022 19:33:47 - (UTC)
From:mlel...@serpens.de (Michael van Elst)
Message-ID:
| - if (ver_rel == 0 && ver_patch != 0) {
| + if (ver_maj >= 9) {
I'd suggest instead
if (ver_min == 99) {
While this issue
Date:Fri, 16 Sep 2022 23:46:59 +
From:David Holland
Message-ID:
| While it's possible that some of
| these may exist, it's unlikely that there are many of them or that
| they appear anywhere especially important.
That's all encouraging, and yet more
Date:Fri, 16 Sep 2022 12:59:24 -0400
From:"David H. Gutteridge"
Message-ID:
| So there will be information loss there, at minimum. Whether that ends
| up being significant at some point, I guess we can't say.
I would hope not. That is, I am assuming (but
Date:Thu, 15 Sep 2022 23:46:45 -0700 (PDT)
From:Paul Goyette
Message-ID:
| The human-oriented version is used as part of the path to modules
| directory. Need to make sure that the modules set is properly
| populated,
That much I had tested.
| and that
Date:Fri, 16 Sep 2022 11:10:30 +0900
From:Kengo NAKAHARA
Message-ID: <90c3c46e-6668-9644-70c3-0eab2cf1c...@iij.ad.jp>
| Hmm, I will test kernel module building before commit.
Sorry, I wasn't clear - I build everything (modules included) - I just
never actually
Date:Thu, 15 Sep 2022 17:08:52 +0900
From:Kengo NAKAHARA
Message-ID: <279eae4e-79f4-39c0-5279-83d5738b6...@iij.ad.jp>
| Can version bump up to 9.99.100? Is there anything wrong?
It can. There are no issues with the base system (incl xsrc)
I have tested this in
Date:Fri, 19 Aug 2022 12:40:11 +0200
From:=?UTF-8?Q?Pawe=c5=82_Cichowski?=
Message-ID: <56898e46-7714-200b-4528-afffddd6d...@3mdeb.com>
| I've built the kernel and release for evbarm aarch64 from the latest
| sources and ran it on QEMU. Unfortunately, /dev/efi
Date:Fri, 22 Jul 2022 11:24:46 +0100
From:Patrick Welche
Message-ID:
| Having not seen the dreaded turnstile issue in ages, a NetBSD-9.99.99/amd64
| got stuck on shutdown last night with:
How long did you wait?
I have seen situations where it takes 10-15 mins
Date:Sat, 16 Jul 2022 00:48:59 -0400 (EDT)
From:Mouse
Message-ID: <202207160448.aaa09...@stone.rodents-montreal.org>
| That's what I was trying to do with my looking at "X is tstiled waiting
| for Y, who is tstiled waiting for Z, who is..." and looking at the
|
NetBSD implements overcommitted swap - many processes malloc()
(or mmap() which that really becomes in the current implementation)
far more memory than they're ever going to actually use. It is only
when some real physical memory is required (rather than simply a marker
"zero filled page might be
Date:Fri, 14 Jan 2022 06:22:11 + (UTC)
From:RVP
Message-ID: <8ad9feaf-a513-d33d-c887-3ca8407c...@sdf.org>
| It does not, and wasn't meant to. I noticed that d_type was being
| set to VREG and attached a patch for that to my reply.
Oh. Then apologies. I saw
Date:Thu, 13 Jan 2022 21:12:51 + (UTC)
From:RVP
Message-ID:
| The patch is for processes to know that stat() will have to be
| called for that particular dirent.
Yes, I understood the patch. But why?
| DT_REG would not be right there.
Not always. No.
Date:Thu, 13 Jan 2022 06:52:01 + (UTC)
From:RVP
Message-ID: <91af8c4-d0bd-c31d-6b6a-355826d5...@sdf.org>
| The EINVAL is caused by using readlink() on what was a symlink,
| but, is not anymore because the fd now points to a regular file.
The analysis looks
Date:Tue, 11 Jan 2022 22:20:15 +0100
From:Manuel Bouyer
Message-ID:
| > What causes that EINVAL?
|
|
| I'm not sure (somneone suggested that the file descriptor has been closed
| when ls tries to fstat() it, but I can't confirm this).
That should generate
Date:Sat, 18 Sep 2021 15:54:06 -0700
From:Jason Thorpe
Message-ID: <63bf9e95-498a-4389-9a14-2f3c87a51...@me.com>
| I've changed the man pages to state "set for non-blocking I/O".
That should be much better.
| Yes, they're file descriptors, so close(2) gets rid
Date:Sat, 18 Sep 2021 13:21:27 -0700
From:Jason Thorpe
Message-ID: <5e7b8a22-14c2-4dce-ace2-31552f412...@me.com>
| > unless the
| > .Nm
| > object was created with
| > .Dv TFD_NONBLOCK .
|
| I'm using those names, because those are the names used in
Date:Sat, 18 Sep 2021 10:26:29 -0700
From:Jason Thorpe
Message-ID: <986563ad-88c2-41b9-bf69-51b26240b...@me.com>
| https://www.netbsd.org/~thorpej/timerfd.2
This one contains duplicated text...
Because they are associated with a file descriptor, they may
Date:Thu, 09 Sep 2021 11:58:23 +
From:bsdairekii...@posteo.de
Message-ID: <2cbd055de44ea130b54e525543d5d...@posteo.de>
| I have looked NetBSD manual page and find this description since NetBSD
| 5.0 in utimes and since NetBSD 6.0 in utimensat.
I believe
Date:Tue, 07 Sep 2021 22:14:31 +
From:bsdairekii...@posteo.de
Message-ID:
| this page https://man.netbsd.org/utimensat.2 describes this.
|
| > Ideally a new system call will be added that allows the setting of all
| > three times at once.
|
| Where
Date:Wed, 4 Aug 2021 17:52:46 -0700
From:Jason Thorpe
Message-ID: <68ff8737-f347-4a7f-960b-9e4a6ca9e...@me.com>
| It addresses the concerns about compile-time type checking
| by using an anonymous structure constructed in-line
Is there something in the C
And as a possible optional extra, one fairly
easy way to add type checking woukd be to add
an extra dummp printf format string arg, unused
by config_found (would cost one useless ptr
push at each call, but we can bear that), declare
config_fiund __printf_like, and let the compiker
do arg
Date:Mon, 2 Aug 2021 01:36:26 +0100
From:David Brownlee
Message-ID:
| 3) This email takes one of Taylor's suggestions and hangs an explicit
| version on the calls, which should give reasonable forward
| compatibility
That solves the wrong problem, there is
Date:Fri, 28 May 2021 16:49:26 +
From:Kenny
Message-ID:
| I am using NetBSD 9.2 (amd64) with ZFS as file system and I have
| not found a command to change btime for my files.
Don't bother, the birth time is a total waste of space. It is used
by nothing
Date:Thu, 27 May 2021 20:19:06 +
From:"Koning, Paul"
Message-ID: <8765ae3a-b5b7-4b67-82ce-93473a5b9...@dell.com>
| In this particular case it's converting frequency to period,
| that is a sensible conversion.
But it isn't, you can't convert 60 ticks/second
Date:Thu, 27 May 2021 05:05:15 - (UTC)
From:mlel...@serpens.de (Michael van Elst)
Message-ID:
| mlel...@serpens.de (Michael van Elst) writes:
|
| >Either direction mstohz or hztoms should better always round up to
| >guarantee a minimal delay.
|
| And
Date:Sun, 18 Apr 2021 18:58:56 +
From:Andrew Parker
Message-ID: <2245776.bZt9KSGgi3@t470s.local>
| Does anyone else have a working L2ARC?
Sorry, don't even know what that is, and don't (currently anyway) use zfs,
but:
| - interval = hz *
Date:Sun, 11 Apr 2021 18:14:44 - (UTC)
From:mlel...@serpens.de (Michael van Elst)
Message-ID:
| + spb = vnd->sc_geom.vng_secsize / DEV_BSIZE;
Do we know for sure here that vng_secsize >= DEV_BSIZE ?
When I first used unix (long long ago) the drives I
Date:Sun, 11 Apr 2021 14:25:40 - (UTC)
From:mlel...@serpens.de (Michael van Elst)
Message-ID:
| Seems to have been introduced with netbsd-7.
Perhaps, but the effect was probably invisible until Jan this year
when the calculation of ncylinders was corrected -
Date:Sun, 11 Apr 2021 14:25:40 - (UTC)
From:mlel...@serpens.de (Michael van Elst)
Message-ID:
| + dg->dg_secperunit = vnd->sc_size / DEV_BSIZE;
While it shouldn't make any difference for any properly created image
file, make it be
Date:Sun, 11 Apr 2021 15:53:07 +0200
From:Manuel Bouyer
Message-ID:
| On Sun, Apr 11, 2021 at 01:28:46PM -, Michael van Elst wrote:
| > vnd computes a fake geometry based on 1MB cylinders.
|
| Why does this trucates the total number of sectors of the vnd
Date:Mon, 5 Apr 2021 01:14:01 +0200
From:Joerg Sonnenberger
Message-ID:
| That is discussed in the security model Taylor presented a long time
| ago. In short: nothing. In most use cases, you are screwed at this point
| anyway
This is where the disconnect is
Date:Sun, 4 Apr 2021 15:28:13 +
From:Taylor R Campbell
Message-ID: <20210404152814.3c56360...@jupiter.mumble.net>
| you can let NetBSD take care of it automatically
| on subsequent boots by running `/etc/rc.d/random_seed stop' to save a
| seed to disk.)
Is
Date:Mon, 15 Feb 2021 23:18:33 +0100
From:Rhialto
Message-ID:
| A system call with error can return with the carry set and the error and
| short count returned in a separate registers. The carry bit is how
| errors used to be indicated since at least V7 (even
Date:Fri, 05 Feb 2021 20:43:30 -0500
From:Greg Troxel
Message-ID:
| An obvious question is what POSIX requires, pause for `kill -HUP kred` :)
Hey! wiz is the daemon, I'm an angel...
| I think your case (a) is the only conforming behavior and obviously what
Date:Fri, 16 Oct 2020 04:07:31 +
From:"Thomas Mueller"
Message-ID: <20201016052422.e063084...@mail.netbsd.org>
| Should I add ,linux to the end of the procfs line?
You can, but it isn't needed these days -- I used to mount procfs twice,
once without the linux
Date:Thu, 1 Oct 2020 18:57:12 +0200
From:Manuel Bouyer
Message-ID: <20201001165712.ga1...@antioche.eu.org>
| which, basically. means that one should not use reboot, halt or poweroff
| any more ...
And of course, the system must never cash, hang, or suffer a
Date:Sun, 16 Aug 2020 16:13:57 - (UTC)
From:chris...@astron.com (Christos Zoulas)
Message-ID:
| They don't vanish, they get reparented to init(8) which then wakes up
| and reaps them.
That probably would work, approximately, but isn't what's supposed to
Date:Fri, 14 Aug 2020 20:01:18 +0200
From:Edgar =?iso-8859-1?B?RnXf?=
Message-ID: <20200814180117.gq61...@trav.math.uni-bonn.de>
| 3. I don't see where POSIX defines or allows this, but given 2., I'm surely
|missing something.
Actually, I did go take a
Date:Fri, 14 Aug 2020 20:01:18 +0200
From:Edgar =?iso-8859-1?B?RnXf?=
Message-ID: <20200814180117.gq61...@trav.math.uni-bonn.de>
| 3. I don't see where POSIX defines or allows this, but given 2., I'm surely
|missing something.
It is specified to work this
Date:Sun, 12 Jul 2020 13:01:59 +1000
From:Luke Mewburn
Message-ID: <20200712030159.gh12...@mewburn.net>
| | IMHO, permitting braces to be consistently used:
| | - Adds to clarity of intent.
| | - Aids code review.
| | - Avoids gotofail:
Date:Fri, 10 Jul 2020 16:47:28 +0200
From:Rhialto
Message-ID: <20200710144728.gy3...@falu.nl>
| It also seems to be involved in deciding wether to send a SIGTTOU or
| SIGTTIN to a process
Ah, right, thanks ... when I was reviewing uses in the kernel I
was
Date:Tue, 9 Jun 2020 08:23:19 - (UTC)
From:mlel...@serpens.de (Michael van Elst)
Message-ID:
I have spent a little time looking at this now, and I think
it is just all a mess.
| pg_jobc is not a reference counter.
Maybe not technically a "reference" counter,
Date:Mon, 29 Jun 2020 23:22:52 +0200
From:Kamil Rytarowski
Message-ID:
| Ping? This kernel crash is blocking GDB/etc and it is an instant crash.
Sorry, been side-tracked, will get to it soon.
kre
Date:Mon, 15 Jun 2020 22:34:01 +0200
From:Joerg Sonnenberger
Message-ID: <20200615203401.ga91...@bec.de>
| > Running it under ktrace(1) shows it doing a stat(2) for every metadata
| > file in the tree. The machine sounds like it is hitting the disk for
| >
Date:Tue, 9 Jun 2020 14:16:16 -0400
From:Christos Zoulas
Message-ID:
| The FreeBSD refactoring LGTM. It also simplifies the code.
Sorry, been off net all day ... that may very well be the way to go,
but I'd like to understand what is happening with our current
Date:Tue, 9 Jun 2020 17:04:54 +0200
From:Kamil Rytarowski
Message-ID:
| Yes... syzkaller had like 12 different ways to reproduce it.
OK, thanks.
| There is still a race and we randomly go to negative pg_jobc.
I am not at all surprised...
I will look at it
Date:Tue, 9 Jun 2020 14:13:56 +0200
From:Kamil Rytarowski
Message-ID: <85d5e51f-afd1-1038-fd68-2366ff073...@netbsd.org>
| Here is the simplest reproducer crashing the kernel on negative pg_jobc:
I have not looked at this closely yet, but this is likely because
Date:Tue, 19 May 2020 15:14:21 +0200
From:Kamil Rytarowski
Message-ID:
| I've abandoned the intention of changing these values (by adding
| comments, renaming etc).
Good, thank you.
| Once I will have spare time I might look into
| implementing the missing
Date:Tue, 19 May 2020 14:12:31 +0200
From:Kamil Rytarowski
Message-ID: <6874bb63-5146-797f-98b7-b9c497677...@gmx.com>
| Rationale for pointless?
There is no point. What more can I say?
| My points were:
|
| - Clobbering OS that claims the goals of clean
Date:Mon, 18 May 2020 21:11:36 +0200
From:Kamil Rytarowski
Message-ID: <05255347-1c55-2762-aaf6-fec3caf48...@gmx.com>
| Next, I can add my value at the end of list (and before _P_MAXIDTYPE).
Other than this, everything that you propose is pointless. This one
you
Date:Mon, 18 May 2020 19:45:55 +0200
From:Kamil Rytarowski
Message-ID:
| I have got a local use-case for another P_type (premature to discuss it
| in this thread) and I would rather recycle an unused value.
Don't do that, it is just a number, use one that
Date:Sun, 5 Apr 2020 01:26:15 - (UTC)
From:chris...@astron.com (Christos Zoulas)
Message-ID:
| It could be due to tcsh doing its file descriptor dance differently...
| What shell are you using?
When I run tests against HEAD, I use /bin/sh - the only other
Date:Sat, 4 Apr 2020 16:37:08 +0300
From:Andreas Gustafsson
Message-ID: <24200.36228.881611.989...@guava.gson.org>
| Does anyone have an idea why the tests didn't start failing
| immediately when route.c 1.167 was committed, but only after the
| seemingly
Date:Sat, 4 Apr 2020 12:59:54 -0400 (EDT)
From:Mouse
Message-ID: <202004041659.maa21...@stone.rodents-montreal.org>
| I added the #include to a long string of #include "opt_h" lines,
| none of which are conditional on anything, in
|
Date:Thu, 2 Apr 2020 14:54:13 -0400 (EDT)
From:Mouse
Message-ID: <202004021854.oaa20...@stone.rodents-montreal.org>
| Yes, I got a very nice and helpful off-list mail (thank you!) saying,
| approximately, that I needed to have the #include of opt_autoconf.h
|
Date:Mon, 30 Mar 2020 14:25:01 -0400
From:Christos Zoulas
Message-ID: <3d3ac2b9-5e6e-400c-9a4b-10742c90c...@zoulas.com>
| All the tests are failing for you the same way:
| rump.route: SO_RERROR: Socket operation on non-socket
Not all, but quite a few are.
This
Date:Thu, 2 Apr 2020 12:45:35 -0400 (EDT)
From:Mouse
Message-ID: <202004021645.maa22...@stone.rodents-montreal.org>
| But the error makes me reasonably sure it's related to the defflag I
| added to files.kern.
Perhaps. I'd actually like to see the diff for
Date:Thu, 2 Apr 2020 04:11:17 +0200
From:Kamil Rytarowski
Message-ID:
| This is partially enforceable. As once we generate catchall switch like:
|
| case FOO_OP:
| ...
| case BAR_OP:
| ...
|
| a compiler will report error whenever FOO_OP = BAR_OP.
Date:Mon, 30 Mar 2020 14:25:01 -0400
From:Christos Zoulas
Message-ID: <3d3ac2b9-5e6e-400c-9a4b-10742c90c...@zoulas.com>
| All the tests are failing for you the same way:
| rump.route: SO_RERROR: Socket operation on non-socket
| <>I doubt that my gif change
Date:Mon, 30 Mar 2020 20:47:12 -0400
From:Christos Zoulas
Message-ID:
| Unfortunately they still work for me after a clean build. I am going to =
| try to download a standard build...
Does your tree have any uncommitted changes?
(I see the same 200+ tests
Date:Sat, 8 Feb 2020 16:47:42 +0100
From:Kamil Rytarowski
Message-ID:
| We are allowed to fix this in the kernel for everybody:
Indeed we are. And if you want to change things that way, that's fine.
It turns out this one wasn't the actual problem in this
Date:Sun, 12 Jan 2020 22:36:23 -0500 (EST)
From:Mouse
Message-ID: <202001130336.waa17...@stone.rodents-montreal.org>
| I can't recall ever wanting its functionality,
It is used mostly by a lot of the ATF tests.
| and trying to figure out what the dependency
Date:Fri, 22 Nov 2019 01:04:56 +0100
From:Kamil Rytarowski
Message-ID: <1a9d9b40-42fe-be08-d7b3-e6ecead5b...@gmx.com>
| I think that picking C11 terminology is the way forward.
Use a name like that iff the intent is to also exactly match the
semantics implied,
Date:Thu, 21 Nov 2019 19:19:51 +0100
From:Maxime Villard
Message-ID:
| So in the end which name do we use? Are people really unhappy with _racy()?
| At least it has a general meaning, and does not imply atomicity or ordering.
I dislike naming discussions, as in
Date:Mon, 11 Nov 2019 21:32:06 +0100
From:Joerg Sonnenberger
Message-ID: <2019203206.ga4...@bec.de>
| The update needs to be uninterruptable on the local CPU in the sense that
| context switches and interrupts don't tear the R and W part of the RMW cycle
|
Date:Wed, 2 Oct 2019 21:47:38 -0400 (EDT)
From:Mouse
Message-ID: <201910030147.vaa03...@stone.rodents-montreal.org>
John Nemeth said pretty much exactly what I would have said, but
there are a few points on which I would like to expand...
| - Partitions are huge.
1 - 100 of 307 matches
Mail list logo
