Module Name:src
Committed By: nia
Date: Sun Feb 6 07:37:29 UTC 2022
Modified Files:
src/distrib/notes/common: main
Log Message:
Add pf(4) to the "list of features we plan to remove" (eventually)
list in the installation notes. Ironically, the only other thing here
is
Module Name:src
Committed By: nia
Date: Sun Feb 6 07:37:29 UTC 2022
Modified Files:
src/distrib/notes/common: main
Log Message:
Add pf(4) to the "list of features we plan to remove" (eventually)
list in the installation notes. Ironically, the only other thing here
is
Alexander Nasonov writes:
> Brad Spencer wrote:
>> Alexander Nasonov writes:
>> > Are there any downside of mixing legacy and non-legacy mountpoints?
>> > E.g. if my /var is legacy but /var/crash is a normal ZFS mountpoint?
>>
>> That should work fine as long as /var was arranged to be mounted
> Date: Sat, 5 Feb 2022 22:47:30 +0100
> From: Tobias Nygren
>
> On Sat, 5 Feb 2022 15:17:40 +
> Martin Husemann wrote:
>
> > Modified Files:
> > src/sys/kern: subr_autoconf.c
> >
> > Log Message:
> > cfdriver_iattr_count() is only used in a KASSERT, so #ifdef DIAGNOSTIC it.
>
> This
Date:Sat, 5 Feb 2022 22:20:16 +
From:David Brownlee
Message-ID:
| Oops, my earliest unix experience was on a BSD4.3 variant, so I was
| spoiled by ffs and didn't realise the (in this context) helpful v7fs
| behaviour with overlong filename components.
To
Module Name:src
Committed By: christos
Date: Sat Feb 5 23:10:20 UTC 2022
Modified Files:
src/sys/kern: kern_exec.c
Log Message:
Prevent escallation of privilege due to poor handling of argc == 0 in set*id
binaries by refusing to execute them.
To generate a diff of this
Module Name:src
Committed By: christos
Date: Sat Feb 5 23:10:20 UTC 2022
Modified Files:
src/sys/kern: kern_exec.c
Log Message:
Prevent escallation of privilege due to poor handling of argc == 0 in set*id
binaries by refusing to execute them.
To generate a diff of this
On Wed, 2 Feb 2022 at 17:24, Robert Elz wrote:
>
> Date:Wed, 2 Feb 2022 15:26:21 +
> From:David Brownlee
> Message-ID:
>
>
> | So, we just need an optional flag when mounting v7fs to truncate any
> | looked up filename component to 14 characters
>
> That's
On Sat, 5 Feb 2022 15:17:40 +
Martin Husemann wrote:
> Modified Files:
> src/sys/kern: subr_autoconf.c
>
> Log Message:
> cfdriver_iattr_count() is only used in a KASSERT, so #ifdef DIAGNOSTIC it.
This doesn't seem to work as intended.
In a kernel with "no options DIAGNOSTIC" I now
Brad Spencer wrote:
> Alexander Nasonov writes:
> > Are there any downside of mixing legacy and non-legacy mountpoints?
> > E.g. if my /var is legacy but /var/crash is a normal ZFS mountpoint?
>
> That should work fine as long as /var was arranged to be mounted first.
> The other way around may
Module Name:src
Committed By: hannken
Date: Sat Feb 5 17:32:59 UTC 2022
Modified Files:
src/sys/dev/scsipi: scsiconf.c
Log Message:
Initialize "replun" -- found with KMSAN.
To generate a diff of this commit:
cvs rdiff -u -r1.297 -r1.298 src/sys/dev/scsipi/scsiconf.c
Module Name:src
Committed By: hannken
Date: Sat Feb 5 17:32:59 UTC 2022
Modified Files:
src/sys/dev/scsipi: scsiconf.c
Log Message:
Initialize "replun" -- found with KMSAN.
To generate a diff of this commit:
cvs rdiff -u -r1.297 -r1.298 src/sys/dev/scsipi/scsiconf.c
Module Name:src
Committed By: riastradh
Date: Sat Feb 5 15:29:50 UTC 2022
Modified Files:
src/sys/kern: kern_ntptime.c
Log Message:
kernel: Avoid arithmetic overflow in ntp_adjtime.
Reported-by: syzbot+f4343a1c91ddfe8bb...@syzkaller.appspotmail.com
To generate a diff
Module Name:src
Committed By: riastradh
Date: Sat Feb 5 15:29:50 UTC 2022
Modified Files:
src/sys/kern: kern_ntptime.c
Log Message:
kernel: Avoid arithmetic overflow in ntp_adjtime.
Reported-by: syzbot+f4343a1c91ddfe8bb...@syzkaller.appspotmail.com
To generate a diff
Module Name:src
Committed By: martin
Date: Sat Feb 5 15:17:40 UTC 2022
Modified Files:
src/sys/kern: subr_autoconf.c
Log Message:
cfdriver_iattr_count() is only used in a KASSERT, so #ifdef DIAGNOSTIC it.
To generate a diff of this commit:
cvs rdiff -u -r1.292 -r1.293
Module Name:src
Committed By: martin
Date: Sat Feb 5 15:17:40 UTC 2022
Modified Files:
src/sys/kern: subr_autoconf.c
Log Message:
cfdriver_iattr_count() is only used in a KASSERT, so #ifdef DIAGNOSTIC it.
To generate a diff of this commit:
cvs rdiff -u -r1.292 -r1.293
Module Name:src
Committed By: zafer
Date: Sat Feb 5 14:11:52 UTC 2022
Modified Files:
src/sys/fs/v7fs: v7fs_vfsops.c
Log Message:
fix membername in dprintf
To generate a diff of this commit:
cvs rdiff -u -r1.17 -r1.18 src/sys/fs/v7fs/v7fs_vfsops.c
Please note that
Module Name:src
Committed By: zafer
Date: Sat Feb 5 14:11:52 UTC 2022
Modified Files:
src/sys/fs/v7fs: v7fs_vfsops.c
Log Message:
fix membername in dprintf
To generate a diff of this commit:
cvs rdiff -u -r1.17 -r1.18 src/sys/fs/v7fs/v7fs_vfsops.c
Please note that
Alexander Nasonov writes:
> J. Hannken-Illjes wrote:
>> What is wrong with ZFS legacy mounts?
>>
>> $ zpool create -m legacy tank
>> $ zfs create tank/a
>> $ mount -t zfs tank/a /mnt
>
> Hmm, I heard about ZFS legacy (quite a while ago!) but I didn't
> look into it because, well,
J. Hannken-Illjes wrote:
> What is wrong with ZFS legacy mounts?
>
> $ zpool create -m legacy tank
> $ zfs create tank/a
> $ mount -t zfs tank/a /mnt
Hmm, I heard about ZFS legacy (quite a while ago!) but I didn't
look into it because, well, "legacy"...
Are there any downside of mixing
On Fri, Feb 04, 2022 at 10:19:03PM +, Alexander Nasonov wrote:
> These two "styles of mounting" are
>
> /sbin/mount /filesystem - looks up fs parameters in /etc/fstab
> /sbin/zfs mount dataset - looks up fs parameters in zpools
There are several things that could be done here. I would guess
Module Name:src
Committed By: rillig
Date: Sat Feb 5 10:41:15 UTC 2022
Modified Files:
src/usr.bin/make/unit-tests: var-scope-local.mk
Log Message:
tests/make: document and try to reproduce the crash in Parse_IsVar
Fixed in parse.c 1.662 from today. To actually crash
Module Name:src
Committed By: rillig
Date: Sat Feb 5 10:41:15 UTC 2022
Modified Files:
src/usr.bin/make/unit-tests: var-scope-local.mk
Log Message:
tests/make: document and try to reproduce the crash in Parse_IsVar
Fixed in parse.c 1.662 from today. To actually crash
> On 4. Feb 2022, at 23:19, Alexander Nasonov wrote:
>
> Martin Husemann wrote:
>> On Thu, Feb 03, 2022 at 11:10:43PM +, Alexander Nasonov wrote:
>>> variable, it will mix two very different styles of mounting and
>>> compilate the code.
>
> s/compilate/complicate/
>
>> "different styles
24 matches
Mail list logo
