Searched hist:1.139 (Results 1 - 25 of 478) sorted by relevance

1234567891011>>

/src/sys/net/
H A Dif_gif.c1.139 Mon Feb 12 15:38:14 GMT 2018 maxv branches: 1.139.2;
Use m_freem instead of m_free. Otherwise we're leaking the next mbufs in
the chain.

1.139 Mon Feb 12 15:38:14 GMT 2018 maxv branches: 1.139.2;
Use m_freem instead of m_free. Otherwise we're leaking the next mbufs in
the chain.

/src/sys/dev/mii/
H A Dmiidevs_data.h1.139 Thu Jun 06 16:05:45 GMT 2019 thorpej branches: 1.139.2;
Regen for addition of BCM53125 switch.

1.139 Thu Jun 06 16:05:45 GMT 2019 thorpej branches: 1.139.2;
Regen for addition of BCM53125 switch.

H A Dmiidevs.h1.139 Wed Feb 13 04:35:58 GMT 2019 msaitoh Regen.

/src/sys/arch/sun3/conf/
H A DGENERIC1.139 Wed Jul 18 15:48:49 GMT 2007 tsutsui branches: 1.139.4; 1.139.6; 1.139.10;
- add options COMPAT_40
- use options<space><tab>

1.139 Wed Jul 18 15:48:49 GMT 2007 tsutsui branches: 1.139.4; 1.139.6; 1.139.10;
- add options COMPAT_40
- use options<space><tab>

1.139 Wed Jul 18 15:48:49 GMT 2007 tsutsui branches: 1.139.4; 1.139.6; 1.139.10;
- add options COMPAT_40
- use options<space><tab>

1.139 Wed Jul 18 15:48:49 GMT 2007 tsutsui branches: 1.139.4; 1.139.6; 1.139.10;
- add options COMPAT_40
- use options<space><tab>

/src/sys/arch/vax/vax/
H A Dtrap.c1.143 Sat Apr 05 11:20:30 GMT 2025 riastradh vax/trap.c: Restore revisions 1.139 and 1.141: zero regs on exec.

I backed these out because the vax releng testbed seemed unhappy.
But the unhappiness of the testbed seems unrelated: backing out the
change didn't resolve it, and the symptoms were already there before
the change, so I think they are unrelated:

(before)

kernel/t_umountstress (125/980): 2 test cases
fileop: [ 5236.4300030] vnd0: no disk label
Traceback (most recent call last):
...
pexpect.exceptions.TIMEOUT: Timeout exceeded.

https://releng.netbsd.org/b5reports/vax/2025/2025.03.04.07.42.19/test.log

(after)

kernel/t_umountstress (125/980): 2 test cases
fileop: [ 5012.1700030] vnd0: no disk label
Traceback (most recent call last):
...
pexpect.exceptions.TIMEOUT: Timeout exceeded.

https://releng.netbsd.org/b5reports/vax/2025/2025.03.22.13.28.35/test.log

(most recent, with the change reverted)

kernel/t_umountstress (126/983): 2 test cases
fileop: [ 5516.6200030] vnd0: no disk label
[ 5517.1500030] ra0: drive 0 hard error datagram: memory addr 0x5000: host buffer access error (non-exist. memory) (code 9, subcode 3)
[ 5517.1500030] ra0: host buffer access error (non-exist. memory) (code 9, subcode 3)
[7.680000s] Failed: atf-check failed; see the output of the test for details
mountlist: [ 5524.4600030] vnd0: no disk label
Traceback (most recent call last):

pexpect.exceptions.TIMEOUT: Timeout exceeded.

https://releng.netbsd.org/b5reports/vax/2025/2025.04.01.03.16.41/test.log

1.142 Sat Mar 29 00:16:30 GMT 2025 riastradh vax/trap.c: Back out revisions 1.139 and 1.141 for now.

These changes served to zero registers on exec in order to avoid
leaking secret register content to the replacement process image.

Unfortunately, I did not adequately test these changes, and the vax
testbed has been unhappy since they went in. It's possible they're
not the culprit -- it's possible that 1.141 (setting PSL_U|PSL_PREVU)
was enough to fix the bug introduced by 1.139 -- but let's just try
backing both out so we can let the releng testbed figure out for me
whether to go chasing other parts of the trapframe to set up
(tf_trap=T_SYSCALL? tf_code=???) or this is a wild goose chase and
it's actually something else broken.

PR kern/59084: exec/spawn leaks register content

1.142 Sat Mar 29 00:16:30 GMT 2025 riastradh vax/trap.c: Back out revisions 1.139 and 1.141 for now.

These changes served to zero registers on exec in order to avoid
leaking secret register content to the replacement process image.

Unfortunately, I did not adequately test these changes, and the vax
testbed has been unhappy since they went in. It's possible they're
not the culprit -- it's possible that 1.141 (setting PSL_U|PSL_PREVU)
was enough to fix the bug introduced by 1.139 -- but let's just try
backing both out so we can let the releng testbed figure out for me
whether to go chasing other parts of the trapframe to set up
(tf_trap=T_SYSCALL? tf_code=???) or this is a wild goose chase and
it's actually something else broken.

PR kern/59084: exec/spawn leaks register content

1.139 Sun Mar 16 15:35:00 GMT 2025 riastradh Clear trapframe on exec.

Do this for all architectures, even if the trapframe is fully
initialized -- makes it easier to audit and be confident it's
correct, and most likely (with the exception of sh3 which has an
intermediate call to ufetch_int in the middle) the compiler can
eliminate redundant stores in these routines.

PR kern/59084: exec/spawn leaks register content

/src/sys/arch/sparc/dev/
H A Dfd.c1.139 Wed Jan 02 11:48:28 GMT 2008 ad branches: 1.139.6; 1.139.8; 1.139.10;
Merge vmlocking2 to head.

1.139 Wed Jan 02 11:48:28 GMT 2008 ad branches: 1.139.6; 1.139.8; 1.139.10;
Merge vmlocking2 to head.

1.139 Wed Jan 02 11:48:28 GMT 2008 ad branches: 1.139.6; 1.139.8; 1.139.10;
Merge vmlocking2 to head.

1.139 Wed Jan 02 11:48:28 GMT 2008 ad branches: 1.139.6; 1.139.8; 1.139.10;
Merge vmlocking2 to head.

/src/sys/fs/udf/
H A Dudf_subr.c1.139 Sat Apr 01 19:35:56 GMT 2017 riastradh branches: 1.139.6; 1.139.12;
KASSERT(mutex_owned(vp->v_interlock)) in vnode iterator selector.

1.139 Sat Apr 01 19:35:56 GMT 2017 riastradh branches: 1.139.6; 1.139.12;
KASSERT(mutex_owned(vp->v_interlock)) in vnode iterator selector.

1.139 Sat Apr 01 19:35:56 GMT 2017 riastradh branches: 1.139.6; 1.139.12;
KASSERT(mutex_owned(vp->v_interlock)) in vnode iterator selector.

/src/sys/arch/hp300/hp300/
H A Dtrap.c1.139 Wed Oct 15 06:51:17 GMT 2008 wrstuden branches: 1.139.2; 1.139.4;
Merge wrstuden-revivesa into HEAD.

1.139 Wed Oct 15 06:51:17 GMT 2008 wrstuden branches: 1.139.2; 1.139.4;
Merge wrstuden-revivesa into HEAD.

1.139 Wed Oct 15 06:51:17 GMT 2008 wrstuden branches: 1.139.2; 1.139.4;
Merge wrstuden-revivesa into HEAD.

/src/sys/arch/i386/conf/
H A DMakefile.i3861.139 Wed Jun 22 06:14:51 GMT 2005 dyoung branches: 1.139.2; 1.139.4;
Resolve conflicts in importation of 18-May-2005 ath(4) / net80211(9)
from FreeBSD. Introduce compatibility shims (sys/dev/ic/ath_netbsd.[ch],
sys/net80211/ieee80211_netbsd.[ch]). Update drivers (an, atu, atw,
awi, ipw, iwi, rtw, wi) for the new net80211(9) API.
1.139 Wed Jun 22 06:14:51 GMT 2005 dyoung branches: 1.139.2; 1.139.4;
Resolve conflicts in importation of 18-May-2005 ath(4) / net80211(9)
from FreeBSD. Introduce compatibility shims (sys/dev/ic/ath_netbsd.[ch],
sys/net80211/ieee80211_netbsd.[ch]). Update drivers (an, atu, atw,
awi, ipw, iwi, rtw, wi) for the new net80211(9) API.
1.139 Wed Jun 22 06:14:51 GMT 2005 dyoung branches: 1.139.2; 1.139.4;
Resolve conflicts in importation of 18-May-2005 ath(4) / net80211(9)
from FreeBSD. Introduce compatibility shims (sys/dev/ic/ath_netbsd.[ch],
sys/net80211/ieee80211_netbsd.[ch]). Update drivers (an, atu, atw,
awi, ipw, iwi, rtw, wi) for the new net80211(9) API.
/src/sys/arch/mac68k/mac68k/
H A Dtrap.c1.139 Mon Nov 23 00:11:44 GMT 2009 rmind branches: 1.139.2; 1.139.4;
Use lwp_getpcb() on m68k ports, clean from struct user usage.

1.139 Mon Nov 23 00:11:44 GMT 2009 rmind branches: 1.139.2; 1.139.4;
Use lwp_getpcb() on m68k ports, clean from struct user usage.

1.139 Mon Nov 23 00:11:44 GMT 2009 rmind branches: 1.139.2; 1.139.4;
Use lwp_getpcb() on m68k ports, clean from struct user usage.

/src/sys/sys/
H A Dexec.h1.139 Sun Aug 05 01:43:59 GMT 2012 matt branches: 1.139.2; 1.139.4;
back out elf note changes and use EF_ARM_ABIVERS to determine EABI usage.

1.139 Sun Aug 05 01:43:59 GMT 2012 matt branches: 1.139.2; 1.139.4;
back out elf note changes and use EF_ARM_ABIVERS to determine EABI usage.

1.139 Sun Aug 05 01:43:59 GMT 2012 matt branches: 1.139.2; 1.139.4;
back out elf note changes and use EF_ARM_ABIVERS to determine EABI usage.

H A DMakefile1.140 Wed Nov 02 19:21:43 GMT 2011 yamt branches: 1.140.4;
revert rev.1.139, which i mistakenly committed with the unrelated change.

1.139 Wed Nov 02 13:52:34 GMT 2011 yamt branches: 1.139.2;
buf_inorder:
- make the return value bool
- comments

1.139 Wed Nov 02 13:52:34 GMT 2011 yamt branches: 1.139.2;
buf_inorder:
- make the return value bool
- comments

H A Dsyscallargs.h1.139 Sun May 29 21:11:30 GMT 2005 christos branches: 1.139.2;
Regen
1.139 Sun May 29 21:11:30 GMT 2005 christos branches: 1.139.2;
Regen
/src/sys/dev/ic/
H A Datw.c1.139 Wed Apr 30 14:07:13 GMT 2008 ad branches: 1.139.2; 1.139.4; 1.139.6;
Make various bits of debug code compile again.

1.139 Wed Apr 30 14:07:13 GMT 2008 ad branches: 1.139.2; 1.139.4; 1.139.6;
Make various bits of debug code compile again.

1.139 Wed Apr 30 14:07:13 GMT 2008 ad branches: 1.139.2; 1.139.4; 1.139.6;
Make various bits of debug code compile again.

1.139 Wed Apr 30 14:07:13 GMT 2008 ad branches: 1.139.2; 1.139.4; 1.139.6;
Make various bits of debug code compile again.

/src/sys/dev/isa/
H A Disa.c1.139 Sat Apr 24 23:36:55 GMT 2021 thorpej branches: 1.139.8;
Merge thorpej-cfargs branch:

Simplify and make extensible the config_search() / config_found() /
config_attach() interfaces: rather than having different variants for
which arguments you want pass along, just have a single call that
takes a variadic list of tag-value arguments.

Adjust all call sites:
- Simplify wherever possible; don't pass along arguments that aren't
actually needed.
- Don't be explicit about what interface attribute is attaching if
the device only has one. (More simplification.)
- Add a config_probe() function to be used in indirect configuiration
situations, making is visibly easier to see when indirect config is
in play, and allowing for future change in semantics. (As of now,
this is just a wrapper around config_match(), but that is an
implementation detail.)

Remove unnecessary or redundant interface attributes where they're not
needed.

There are currently 5 "cfargs" defined:
- CFARG_SUBMATCH (submatch function for direct config)
- CFARG_SEARCH (search function for indirect config)
- CFARG_IATTR (interface attribte)
- CFARG_LOCATORS (locators array)
- CFARG_DEVHANDLE (devhandle_t - wraps OFW, ACPI, etc. handles)

...and a sentinel value CFARG_EOL.

Add some extra sanity checking to ensure that interface attributes
aren't ambiguous.

Use CFARG_DEVHANDLE in MI FDT, OFW, and ACPI code, and macppc and shark
ports to associate those device handles with device_t instance. This
will trickle trough to more places over time (need back-end for pre-OFW
Sun OBP; any others?).

1.139 Sat Apr 24 23:36:55 GMT 2021 thorpej branches: 1.139.8;
Merge thorpej-cfargs branch:

Simplify and make extensible the config_search() / config_found() /
config_attach() interfaces: rather than having different variants for
which arguments you want pass along, just have a single call that
takes a variadic list of tag-value arguments.

Adjust all call sites:
- Simplify wherever possible; don't pass along arguments that aren't
actually needed.
- Don't be explicit about what interface attribute is attaching if
the device only has one. (More simplification.)
- Add a config_probe() function to be used in indirect configuiration
situations, making is visibly easier to see when indirect config is
in play, and allowing for future change in semantics. (As of now,
this is just a wrapper around config_match(), but that is an
implementation detail.)

Remove unnecessary or redundant interface attributes where they're not
needed.

There are currently 5 "cfargs" defined:
- CFARG_SUBMATCH (submatch function for direct config)
- CFARG_SEARCH (search function for indirect config)
- CFARG_IATTR (interface attribte)
- CFARG_LOCATORS (locators array)
- CFARG_DEVHANDLE (devhandle_t - wraps OFW, ACPI, etc. handles)

...and a sentinel value CFARG_EOL.

Add some extra sanity checking to ensure that interface attributes
aren't ambiguous.

Use CFARG_DEVHANDLE in MI FDT, OFW, and ACPI code, and macppc and shark
ports to associate those device handles with device_t instance. This
will trickle trough to more places over time (need back-end for pre-OFW
Sun OBP; any others?).

/src/sbin/
H A DMakefile1.139 Mon Jun 06 13:28:55 GMT 2022 nia branches: 1.139.4;
revert bits and pieces I accidentally included in my last commit

from hannken

1.139 Mon Jun 06 13:28:55 GMT 2022 nia branches: 1.139.4;
revert bits and pieces I accidentally included in my last commit

from hannken

/src/distrib/sets/lists/base/
H A Dmd.i3861.139 Wed Aug 17 00:33:52 GMT 2011 jakllsch branches: 1.139.2;
Add ./usr/mdec/gptmbr.bin obsoleting mbr_gpt and mbr_gpt_com0.
1.139 Wed Aug 17 00:33:52 GMT 2011 jakllsch branches: 1.139.2;
Add ./usr/mdec/gptmbr.bin obsoleting mbr_gpt and mbr_gpt_com0.
/src/include/
H A DMakefile1.139 Sat Feb 11 23:31:24 GMT 2012 martin branches: 1.139.6;
Add userland part of posix_spawn. Libc functions imported from FreeBSD.
Based on Charles Zhang's summer of code project.

1.139 Sat Feb 11 23:31:24 GMT 2012 martin branches: 1.139.6;
Add userland part of posix_spawn. Libc functions imported from FreeBSD.
Based on Charles Zhang's summer of code project.

/src/share/man/man7/
H A Dsysctl.71.139 Sat Jun 01 19:54:34 GMT 2019 kamil branches: 1.139.2;
Document KERN_PROC_CWD in sysctl(7)

1.139 Sat Jun 01 19:54:34 GMT 2019 kamil branches: 1.139.2;
Document KERN_PROC_CWD in sysctl(7)

/src/sys/uvm/
H A Duvm_mmap.c1.139 Fri Oct 14 09:23:31 GMT 2011 hannken branches: 1.139.2; 1.139.6;
Change the vnode locking protocol of VOP_GETATTR() to request at least
a shared lock. Make all calls outside of file systems respect it.

The calls from file systems need review.

No objections from tech-kern.

1.139 Fri Oct 14 09:23:31 GMT 2011 hannken branches: 1.139.2; 1.139.6;
Change the vnode locking protocol of VOP_GETATTR() to request at least
a shared lock. Make all calls outside of file systems respect it.

The calls from file systems need review.

No objections from tech-kern.

1.139 Fri Oct 14 09:23:31 GMT 2011 hannken branches: 1.139.2; 1.139.6;
Change the vnode locking protocol of VOP_GETATTR() to request at least
a shared lock. Make all calls outside of file systems respect it.

The calls from file systems need review.

No objections from tech-kern.

/src/sys/arch/x68k/x68k/
H A Dmachdep.c1.139 Mon Mar 05 20:51:11 GMT 2007 he branches: 1.139.2; 1.139.4;
Cast to char* before doing pointer arithmetic.

1.139 Mon Mar 05 20:51:11 GMT 2007 he branches: 1.139.2; 1.139.4;
Cast to char* before doing pointer arithmetic.

1.139 Mon Mar 05 20:51:11 GMT 2007 he branches: 1.139.2; 1.139.4;
Cast to char* before doing pointer arithmetic.

/src/sys/arch/atari/atari/
H A Dmachdep.c1.139 Sat Dec 24 22:45:34 GMT 2005 perry branches: 1.139.20; 1.139.22;
bare asm -> __asm

1.139 Sat Dec 24 22:45:34 GMT 2005 perry branches: 1.139.20; 1.139.22;
bare asm -> __asm

1.139 Sat Dec 24 22:45:34 GMT 2005 perry branches: 1.139.20; 1.139.22;
bare asm -> __asm

/src/sys/dev/usb/
H A Duaudio.c1.139 Fri Sep 27 13:34:48 GMT 2013 skrll branches: 1.139.4; 1.139.8;
Don't call mutex_spin_exit on already released lock.

1.139 Fri Sep 27 13:34:48 GMT 2013 skrll branches: 1.139.4; 1.139.8;
Don't call mutex_spin_exit on already released lock.

1.139 Fri Sep 27 13:34:48 GMT 2013 skrll branches: 1.139.4; 1.139.8;
Don't call mutex_spin_exit on already released lock.

H A Dugen.c1.139 Mon Mar 05 09:35:01 GMT 2018 ws branches: 1.139.2; 1.139.4;
Fix last:

Since config(1) could not distinguish between device and
interface attachments, it was generating only the latter.
Thus devices without their own driver wouldn't match the
ugen driver anymore.

Fix this by using a different device name for interface attachments.

1.139 Mon Mar 05 09:35:01 GMT 2018 ws branches: 1.139.2; 1.139.4;
Fix last:

Since config(1) could not distinguish between device and
interface attachments, it was generating only the latter.
Thus devices without their own driver wouldn't match the
ugen driver anymore.

Fix this by using a different device name for interface attachments.

1.139 Mon Mar 05 09:35:01 GMT 2018 ws branches: 1.139.2; 1.139.4;
Fix last:

Since config(1) could not distinguish between device and
interface attachments, it was generating only the latter.
Thus devices without their own driver wouldn't match the
ugen driver anymore.

Fix this by using a different device name for interface attachments.

/src/sys/ufs/ufs/
H A Dufs_vnops.c1.139 Wed Mar 01 00:38:33 GMT 2006 yamt branches: 1.139.2; 1.139.4; 1.139.6;
merge yamt-uio_vmspace branch.

- use vmspace rather than proc or lwp where appropriate.
the latter is more natural to specify an address space.
(and less likely to be abused for random purposes.)
- fix a swdmover race.

1.139 Wed Mar 01 00:38:33 GMT 2006 yamt branches: 1.139.2; 1.139.4; 1.139.6;
merge yamt-uio_vmspace branch.

- use vmspace rather than proc or lwp where appropriate.
the latter is more natural to specify an address space.
(and less likely to be abused for random purposes.)
- fix a swdmover race.

1.139 Wed Mar 01 00:38:33 GMT 2006 yamt branches: 1.139.2; 1.139.4; 1.139.6;
merge yamt-uio_vmspace branch.

- use vmspace rather than proc or lwp where appropriate.
the latter is more natural to specify an address space.
(and less likely to be abused for random purposes.)
- fix a swdmover race.

1.139 Wed Mar 01 00:38:33 GMT 2006 yamt branches: 1.139.2; 1.139.4; 1.139.6;
merge yamt-uio_vmspace branch.

- use vmspace rather than proc or lwp where appropriate.
the latter is more natural to specify an address space.
(and less likely to be abused for random purposes.)
- fix a swdmover race.

Completed in 202 milliseconds

1234567891011>>