Skip to contentSkip to conversation

UFS maintainer and a bug in ufs/super.c

DISCUSSION Tobias Klausmann 2 participants 3 messages Apr 17, 2002 – Apr 30, 2002 VFS

lore
Share & tools
lore
#0 lore raw

Hi!

First off: Is Daniel Pirkl <[email protected]> still the official UFS maintainer? If not whom do I send the stuff below to? I tried to contact Daniel but haven't heard back from him in a while. The list archives contain another message by someone who was seeking out the UFS maintainer but never got an answer.

The problem is this:
Read support for UFS assumes that fs_bsize is one of 4096, 8192, 32768. Now this worked for a long time, but recently, FreeBSD ships with a newfs(8) that uses a fs_bsize of 16384 by default.

I don't know why 16834 is omitted in ufs/super.c, but inserting the numbers in the appropriate places at least fixes read support. Given the thoroughly experimental nature of write support, I didn't try to mess with that.

So, whom do I send the patch to?

Greets,
Tobias

Signature · 1 line
Eat drink and be merry, for tomorrow we diet.
#1 lore raw

Hi!

Quoted 7 lines · Tobias Klausmann

Hi!

First off: Is Daniel Pirkl <[email protected]> still the official UFS maintainer? If not whom do I send the stuff below to? I tried to contact Daniel but haven't heard back from him in a while. The list archives contain another message by someone who was seeking out the UFS maintainer but never got an answer.

Neither did I get one here. Why? Is xBSD an OS non grata? I mean... it's a bloody 7 character patch! At least some pointer would have been helpful.

This is not a high-volume list, so to me it looks like people just don't give a rat's ass. VERY disappointing, guys.

Quoted 11 lines

The problem is this:
Read support for UFS assumes that fs_bsize is one of 4096, 8192, 32768. Now this worked for a long time, but recently, FreeBSD ships with a newfs(8) that uses a fs_bsize of 16384 by default.

I don't know why 16834 is omitted in ufs/super.c, but inserting the numbers in the appropriate places at least fixes read support. Given the thoroughly experimental nature of write support, I didn't try to mess with that.

So, whom do I send the patch to?

The question remains unanswered.

#2 lore raw
Quoted 5 lines · Tobias Klausmann

I mean... it's a bloody 7 character patch! At least some pointer would have been helpful.

This is not a high-volume list, so to me it looks like people just don't give a rat's ass. VERY disappointing, guys.

What about actually sending the patch instead of attaching tarballs?