>
> This code could have done that - implemented linux's clone3() and then
> redefined clone() to be a particular way of calling clone3() (which is
> what I'd guess linux implementations might do, if they don't just have
> both versions in full). That would have worked, but requires updating
>
Date:Mon, 30 Sep 2024 09:09:04 -0400
From:Christos Zoulas
Message-ID: <2f4ec894-d66f-4608-84b1-7dd8433eb...@zoulas.com>
| [quoting mrg@]
| > this looks like it should use NETBSD32IPTR64(),
No, that would be wrong (even if it happened to work), it is expecting
to
> On Sep 29, 2024, at 10:27 PM, matthew green wrote:
>
> thanks for fixing the build.
>
> "Robert Elz" writes:
>> Module Name: src
>> Committed By:kre
>> Date:Mon Sep 30 01:26:48 UTC 2024
>>
>> Modified Files:
>> src/sys/compat/linux/common: linux_sched.c
>>
>> L
thanks for fixing the build.
"Robert Elz" writes:
> Module Name: src
> Committed By: kre
> Date: Mon Sep 30 01:26:48 UTC 2024
>
> Modified Files:
> src/sys/compat/linux/common: linux_sched.c
>
> Log Message:
> Supply a missing cast, which fixes the i386 (other 32 bit too probably)
>
On 2023-08-25 13:30, Taylor R Campbell wrote:
> Since VOP_READDIR requires vp to be locked, I can infer that the
> handle_write caller must already hold vp locked. But that means that
> we have ifd_lock -> vnode lock in one path, and vnode lock -> ifd_lock
> in another path, which is forbidden (un
> Date: Fri, 25 Aug 2023 13:38:02 -0400
> From: Theodore Preduta
>
> On 2023-08-25 13:13, Taylor R Campbell wrote:
> > This can't be right, and it's a little unsettling that the problem
> > isn't caught by any automatic tests.
> >
> > As I understand it, the `ie_name' member is supposed to provi
On 2023-08-25 13:13, Taylor R Campbell wrote:
>> Module Name:src
>> Committed By: christos
>> Date: Wed Aug 23 19:17:59 UTC 2023
>>
>> Modified Files:
>> src/sys/compat/linux/common: linux_inotify.c
>>
>> Log Message:
>> put variable length structure at the end, so that clan
> Module Name:src
> Committed By: christos
> Date: Thu Aug 24 19:51:24 UTC 2023
>
> Modified Files:
> src/sys/compat/linux/common: linux_inotify.c
>
> Log Message:
> fix a locking bug (Theodore Preduta)
>
> if (needs_lock)
> vn_lock(vp, LK_SHARED |
> Module Name:src
> Committed By: christos
> Date: Wed Aug 23 19:17:59 UTC 2023
>
> Modified Files:
> src/sys/compat/linux/common: linux_inotify.c
>
> Log Message:
> put variable length structure at the end, so that clang does not complain.
>
> struct inotify_entry {
>
On Jan 9, 12:33pm, m...@eterna.com.au (matthew green) wrote:
-- Subject: re: CVS commit: src/sys/compat/linux/common
| Christos Zoulas writes:
| > On Jan 9, 12:44am, m...@netbsd.org (m...@netbsd.org) wrote:
| > -- Subject: Re: CVS commit: src/sys/compat/linux/common
| >
| > | W
Christos Zoulas writes:
> On Jan 9, 12:44am, m...@netbsd.org (m...@netbsd.org) wrote:
> -- Subject: Re: CVS commit: src/sys/compat/linux/common
>
> | Why not add a signal?
>
> It is complicated to do so. It will even change the sigmask size.
it will? don't we have suppo
On Jan 9, 12:44am, m...@netbsd.org (m...@netbsd.org) wrote:
-- Subject: Re: CVS commit: src/sys/compat/linux/common
| Why not add a signal?
It is complicated to do so. It will even change the sigmask size.
christos
> + /*
> + * XXX: Linux has 33 realtime signals, the go binary wants to
> + * reset all of them; nothing else uses the last RT signal, so for
> + * now ignore it.
> + */
> + if (sig == LINUX__NSIG) {
> + uprintf("%s: setting signal %d ignored\n", __func__, si
13 matches
Mail list logo
