>
> 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 {
>
Yes, I committed it (I had the change in my tree).
Best,
christos
> On Aug 21, 2023, at 3:40 PM, Ryo ONODERA wrote:
>
> Hi,
>
> "Christos Zoulas" writes:
>
>> Module Name: src
>> Committed By:christos
>> Date:Sun Aug 20 18:08:57 UTC 2023
>>
>> Modified Files:
>>
Hi,
"Christos Zoulas" writes:
> Module Name: src
> Committed By: christos
> Date: Sun Aug 20 18:08:57 UTC 2023
>
> Modified Files:
> src/sys/compat/linux: files.linux
>
> Log Message:
> add inotify (forgot to commit this)
>
>
> To generate a diff of this commit:
> cvs rdiff -u -r1
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
From: m...@netbsd.org (Emmanuel Dreyfus), Date: Tue, 3 Jan 2017 02:30:17 +0100
> Ryo ONODERA wrote:
>
>> This commit breaks my kernel build.
>> It seems that this commit does not fit with -current's format.
>> Could you regenerate these files again?
>
> What error do you get?
Here is typical e
Ryo ONODERA wrote:
> This commit breaks my kernel build.
> It seems that this commit does not fit with -current's format.
> Could you regenerate these files again?
I was running a build to reproduce the problem, when I noticed martin@
fixed it.
--
Emmanuel Dreyfus
http://hcpnet.free.fr/pubz
m.
Ryo ONODERA wrote:
> This commit breaks my kernel build.
> It seems that this commit does not fit with -current's format.
> Could you regenerate these files again?
What error do you get?
--
Emmanuel Dreyfus
http://hcpnet.free.fr/pubz
m...@netbsd.org
Hi,
This commit breaks my kernel build.
It seems that this commit does not fit with -current's format.
Could you regenerate these files again?
Thank you.
From: "Emmanuel Dreyfus" , Date: Mon, 2 Jan 2017 16:32:39 +
> Module Name: src
> Committed By: manu
> Date: Mon Jan 2 16:32:39
On Sep 26, 8:17pm, m...@m00nbsd.net (Maxime Villard) wrote:
-- Subject: Re: CVS commit: src/sys/compat/linux/arch/i386
| No. You committed this:
|
| if ((t = proc_find(SCARG(uap, pid))) == NULL) {
| mutex_exit(proc_lock);
| - return ESRCH;
| + goto
Le 21/09/2014 18:58, Christos Zoulas a écrit :
>
> Module Name: src
> Committed By: christos
> Date: Sun Sep 21 16:58:42 UTC 2014
>
> Modified Files:
> src/sys/compat/linux/arch/i386: linux_ptrace.c
>
> Log Message:
> fix leak
>
>
> To generate a diff of this commit:
> cvs rdiff
Le 26/09/2014 19:50, Christos Zoulas a écrit :
On Sep 26, 7:29pm, m...@m00nbsd.net (Maxime Villard) wrote:
-- Subject: Re: CVS commit: src/sys/compat/linux/arch/i386
| Looks like I chose the wrong thread, I was talking about
| sys/compat/linux/arch/powerpc/linux_ptrace.c.
line 121?
christos
On Sep 26, 7:29pm, m...@m00nbsd.net (Maxime Villard) wrote:
-- Subject: Re: CVS commit: src/sys/compat/linux/arch/i386
| Looks like I chose the wrong thread, I was talking about
| sys/compat/linux/arch/powerpc/linux_ptrace.c.
line 121?
christos
Le 26/09/2014 19:08, Christos Zoulas a écrit :
On Sep 26, 6:13pm, m...@m00nbsd.net (Maxime Villard) wrote:
-- Subject: Re: CVS commit: src/sys/compat/linux/arch/i386
| Can you tell me where 'error' is initialized?
line 145?
christos
Looks like I chose the wrong thread, I was tal
On Sep 26, 6:13pm, m...@m00nbsd.net (Maxime Villard) wrote:
-- Subject: Re: CVS commit: src/sys/compat/linux/arch/i386
| Can you tell me where 'error' is initialized?
line 145?
christos
On Mon, 18 Nov 2013, Chuck Silvers wrote:
Module Name:src
Committed By: chs
Date: Mon Nov 18 01:32:22 UTC 2013
Modified Files:
src/sys/compat/linux/arch/amd64: linux_exec.h linux_exec_machdep.c
src/sys/compat/linux/common: linux_exec.h linux_exec_elf32.c
Log Mess
26 matches
Mail list logo
