Module Name:src
Committed By: riastradh
Date: Wed Jul 5 10:59:08 UTC 2023
Modified Files:
src/sbin/fsck_ffs: inode.c setup.c utilities.c
Log Message:
Revert "fsck_ffs(8): Ensure A divides S before aligned_alloc(A, S)."
C17 lifted this restriction.
To generate a diff of
Module Name:src
Committed By: riastradh
Date: Wed Jul 5 10:59:08 UTC 2023
Modified Files:
src/sbin/fsck_ffs: inode.c setup.c utilities.c
Log Message:
Revert "fsck_ffs(8): Ensure A divides S before aligned_alloc(A, S)."
C17 lifted this restriction.
To generate a diff of
Module Name:src
Committed By: riastradh
Date: Tue Jul 4 20:40:53 UTC 2023
Modified Files:
src/sbin/fsck_ffs: dir.c extern.h fsck.h inode.c main.c pass1.c pass2.c
pass4.c pass5.c pass6.c quota2.c setup.c utilities.c
Log Message:
fsck_ffs(8): Fix whitespace issu
Module Name:src
Committed By: riastradh
Date: Tue Jul 4 20:40:53 UTC 2023
Modified Files:
src/sbin/fsck_ffs: dir.c extern.h fsck.h inode.c main.c pass1.c pass2.c
pass4.c pass5.c pass6.c quota2.c setup.c utilities.c
Log Message:
fsck_ffs(8): Fix whitespace issu
Module Name:src
Committed By: riastradh
Date: Tue Jul 4 20:40:22 UTC 2023
Modified Files:
src/sbin/fsck_ffs: inode.c setup.c utilities.c
Log Message:
fsck_ffs(8): Ensure A divides S before aligned_alloc(A, S).
Required by C11 Sec. 7.22.3.1 The aligned_alloc function, par
Module Name:src
Committed By: riastradh
Date: Tue Jul 4 20:40:22 UTC 2023
Modified Files:
src/sbin/fsck_ffs: inode.c setup.c utilities.c
Log Message:
fsck_ffs(8): Ensure A divides S before aligned_alloc(A, S).
Required by C11 Sec. 7.22.3.1 The aligned_alloc function, par
Module Name:src
Committed By: chs
Date: Mon Mar 27 22:53:37 UTC 2023
Modified Files:
src/sbin/fsck_ffs: pass2.c
Log Message:
Apply this commit from FreeBSD:
commit 6bae6625e0e06816c80ac4971dfccf0643abe3f0
Author: Kirk McKusick
Date: Wed Aug 17 14:19:59 2022 -0700
Module Name:src
Committed By: chs
Date: Mon Mar 27 22:53:37 UTC 2023
Modified Files:
src/sbin/fsck_ffs: pass2.c
Log Message:
Apply this commit from FreeBSD:
commit 6bae6625e0e06816c80ac4971dfccf0643abe3f0
Author: Kirk McKusick
Date: Wed Aug 17 14:19:59 2022 -0700
Module Name:src
Committed By: kre
Date: Sat Jan 14 17:01:11 UTC 2023
Modified Files:
src/sbin/fsck_ffs: inode.c
Log Message:
Use %zu rather than %lu to print a size_t (should fix i386 build).
But, philosophical question, shouldn't the product of two size_t
variables reall
Module Name:src
Committed By: kre
Date: Sat Jan 14 17:01:11 UTC 2023
Modified Files:
src/sbin/fsck_ffs: inode.c
Log Message:
Use %zu rather than %lu to print a size_t (should fix i386 build).
But, philosophical question, shouldn't the product of two size_t
variables reall
Module Name:src
Committed By: christos
Date: Sat Jan 14 12:12:50 UTC 2023
Modified Files:
src/sbin/fsck_ffs: fsck.h inode.c pass4.c utilities.c
Log Message:
catch up with sign changes in the fs.h
To generate a diff of this commit:
cvs rdiff -u -r1.56 -r1.57 src/sbin/fsck
Module Name:src
Committed By: christos
Date: Sat Jan 14 12:12:50 UTC 2023
Modified Files:
src/sbin/fsck_ffs: fsck.h inode.c pass4.c utilities.c
Log Message:
catch up with sign changes in the fs.h
To generate a diff of this commit:
cvs rdiff -u -r1.56 -r1.57 src/sbin/fsck
Module Name:src
Committed By: chs
Date: Sun Jan 8 05:25:25 UTC 2023
Modified Files:
src/sbin/fsck_ffs: pass5.c setup.c
Log Message:
ufs: more signed/unsigned fixes
Fix the previous signed/unsigned fixes to build on 32-bit,
including applying this commit from FreeBSD:
Module Name:src
Committed By: chs
Date: Sun Jan 8 05:25:25 UTC 2023
Modified Files:
src/sbin/fsck_ffs: pass5.c setup.c
Log Message:
ufs: more signed/unsigned fixes
Fix the previous signed/unsigned fixes to build on 32-bit,
including applying this commit from FreeBSD:
Module Name:src
Committed By: martin
Date: Fri Nov 18 07:41:31 UTC 2022
Modified Files:
src/sbin/fsck_ffs: pass1.c
Log Message:
Fix clearing of permissions when finding unexpected extended attributs
for swapped endian file systems. Ok: chs
To generate a diff of this comm
Module Name:src
Committed By: martin
Date: Fri Nov 18 07:41:31 UTC 2022
Modified Files:
src/sbin/fsck_ffs: pass1.c
Log Message:
Fix clearing of permissions when finding unexpected extended attributs
for swapped endian file systems. Ok: chs
To generate a diff of this comm
Module Name:src
Committed By: martin
Date: Thu Nov 17 18:57:16 UTC 2022
Modified Files:
src/sbin/fsck_ffs: pass1.c
Log Message:
Make the "non-zero exattr fields" message show the inode number.
To generate a diff of this commit:
cvs rdiff -u -r1.60 -r1.61 src/sbin/fsck_ff
Module Name:src
Committed By: martin
Date: Thu Nov 17 18:57:16 UTC 2022
Modified Files:
src/sbin/fsck_ffs: pass1.c
Log Message:
Make the "non-zero exattr fields" message show the inode number.
To generate a diff of this commit:
cvs rdiff -u -r1.60 -r1.61 src/sbin/fsck_ff
Module Name:src
Committed By: dholland
Date: Mon Jul 25 05:15:08 UTC 2022
Modified Files:
src/sbin/fsck_ffs: wapbl.c
Log Message:
Fix misleading fsck_ffs messages about wapbl journal replay.
Apparently fsck doesn't have a way to replay it to its internal memory
only. (Som
Module Name:src
Committed By: dholland
Date: Mon Jul 25 05:15:08 UTC 2022
Modified Files:
src/sbin/fsck_ffs: wapbl.c
Log Message:
Fix misleading fsck_ffs messages about wapbl journal replay.
Apparently fsck doesn't have a way to replay it to its internal memory
only. (Som
Module Name:src
Committed By: mlelstv
Date: Sat Mar 6 11:31:40 UTC 2010
Modified Files:
src/sbin/fsck_ffs: wapbl.c
Log Message:
When clearing a log on failure, not only ask the kernel to ignore an
existing log but to remove it on next mount.
To generate a diff of this c
Module Name:src
Committed By: mlelstv
Date: Sat Mar 6 11:31:40 UTC 2010
Modified Files:
src/sbin/fsck_ffs: wapbl.c
Log Message:
When clearing a log on failure, not only ask the kernel to ignore an
existing log but to remove it on next mount.
To generate a diff of this c
"M. Warner Losh" writes:
> In message: <87r5yv4rqn@snark.cb.piermont.com>
> "Perry E. Metzger" writes:
> :
> : "M. Warner Losh" writes:
> : > What I didn't glean from the discussion is what, exactly, you were
> : > going to do about it and what, exactly, you'd like to harmonize
In message: <87r5yv4rqn@snark.cb.piermont.com>
"Perry E. Metzger" writes:
:
: "M. Warner Losh" writes:
: > What I didn't glean from the discussion is what, exactly, you were
: > going to do about it and what, exactly, you'd like to harmonize with
: > FreeBSD on. It may have been
"M. Warner Losh" writes:
> What I didn't glean from the discussion is what, exactly, you were
> going to do about it and what, exactly, you'd like to harmonize with
> FreeBSD on. It may have been there, but I just missed it.
Documentation. It would involve making all man pages refer consistentl
In message: <20090511015855.gd16...@britannica.bec.de>
Joerg Sonnenberger writes:
: On Sun, May 10, 2009 at 07:51:41PM -0600, M. Warner Losh wrote:
: > I've missed much of the discussion, can someone recap exactly what
: > you'd like to see changed? That would be the starting point fo
On Sun, May 10, 2009 at 07:51:41PM -0600, M. Warner Losh wrote:
> I've missed much of the discussion, can someone recap exactly what
> you'd like to see changed? That would be the starting point for any
> user-visisble changes to FreeBSD...
There is currently a mixed naming convention when referi
In message: <20090510220227.gd16...@britannica.bec.de>
Joerg Sonnenberger writes:
: On Sun, May 10, 2009 at 04:31:34AM +, YAMAMOTO Takashi wrote:
: > have you tried to convince freebsd guys to use your preferred name?
: > being different creates another layer of confusion.
:
: We
On Sun, May 10, 2009 at 04:31:34AM +, YAMAMOTO Takashi wrote:
> have you tried to convince freebsd guys to use your preferred name?
> being different creates another layer of confusion.
We had a short discussion about this during BSDCan. Kirk didn't mind and
if it should be reasonable to get c
On Sun, May 10, 2009 at 04:31:34AM +, YAMAMOTO Takashi wrote:
| have you tried to convince freebsd guys to use your preferred name?
| being different creates another layer of confusion.
As I explained in my original thread about this issue [1], it is the
inconsistency in use of "ffs" versu
> On Thu, May 07, 2009 at 08:52:40PM +0900, Izumi Tsutsui wrote:
> | lu...@netbsd.org wrote:
> |
> | > Modified Files:
> | > src/sbin/fsck_ffs: fsck_ffs.8
> | >
> | > Log Message:
> | > Use "FFSv2" instead of "UFS2".
> |
> | There was a related comment around PR/38192:
(or just use "FFSv2 (UFS2)" etc.) in some man pages and related docs.
(and also add the UFS2 paper into the SEE ALSO section?)
I see both points, and think this is an excellent way to address both of
them.
pgpV50T6scYJU.pgp
Description: PGP signature
lu...@netbsd.org wrote:
> On Thu, May 07, 2009 at 08:52:40PM +0900, Izumi Tsutsui wrote:
> | > Log Message:
> | > Use "FFSv2" instead of "UFS2".
:
> | "FFSv2" seems used only in NetBSD world (derived from lfsv2 or libsa?)
>
> I initiated a discussion related to the inconsistent use of
> "F
On Thu, May 07, 2009 at 08:52:40PM +0900, Izumi Tsutsui wrote:
| lu...@netbsd.org wrote:
|
| > Modified Files:
| > src/sbin/fsck_ffs: fsck_ffs.8
| >
| > Log Message:
| > Use "FFSv2" instead of "UFS2".
|
| There was a related comment around PR/38192:
| http://mail-index.NetB
lu...@netbsd.org wrote:
> Modified Files:
> src/sbin/fsck_ffs: fsck_ffs.8
>
> Log Message:
> Use "FFSv2" instead of "UFS2".
There was a related comment around PR/38192:
http://mail-index.NetBSD.org/source-changes/2008/03/09/msg003309.html
>> do we really want to call it FFSv2?
>> we call
Hi Matt !
That gave me a system with WAPBL and full fsck_ffs after panic - good
old times with new code :-)
How about this fix:
RCS file: /cvsroot/src/sbin/fsck_ffs/setup.c,v
retrieving revision 1.86
diff -u -r1.86 setup.c
--- setup.c 25 Mar 2009 03:42:41 -
Hi Matt !
That gave me a system with WAPBL and full fsck_ffs after panic - good
old times with new code :-)
How about this fix:
RCS file: /cvsroot/src/sbin/fsck_ffs/setup.c,v
retrieving revision 1.86
diff -u -r1.86 setup.c
--- setup.c 25 Mar 2009 03:42:41 - 1.86
+++ setup.c 5
37 matches
Mail list logo
