From: Evgeniy Dushistov <dushistov@mail.ru>
To: Dave Bailey <dsbailey@pacbell.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Problem with ufs nextstep in 2.6.18 (debian)
Date: Thu, 22 Nov 2007 07:19:52 +0300 [thread overview]
Message-ID: <20071122041412.GB9896@rain> (raw)
In-Reply-To: <4743438F.3000904@pacbell.net>
On Tue, Nov 20, 2007 at 12:29:03PM -0800, Dave Bailey wrote:
> This problem has been around since kernel 2.6.16, and I see it in
> 2.6.23.1-10.fc7. It occurs in the ufs_check_page function of ufs/dir.c
> at the Espan test, which seems unnecessary for NextStep/OpenStep
> files systems. The following patch preserves the test for other file
> systems and makes the mount useful for NextStep/OpenStep:
> (against the 2.6.23.1-10.fc7 source tree)
>
> dsb@Zeno-Dyn[1012]$ diff dir.c dir.c.orig
> 108,110d107
> < unsigned mnext = UFS_SB(sb)->s_mount_opt &
> < (UFS_MOUNT_UFSTYPE_NEXTSTEP || UFS_MOUNT_UFSTYPE_NEXTSTEP_CD ||
> < UFS_MOUNT_UFSTYPE_OPENSTEP);
> 131c128
> < if ((mnext == 0) & (((offs + rec_len - 1) ^ offs) &
> ~chunk_mask))
> ---
> > if (((offs + rec_len - 1) ^ offs) & ~chunk_mask)
This fixes only symptom, not illness.
This check represent what code think about filesystem layout.
On what actually kind of UFS system did you test this patch?
When I sometime ago fixed similar issue for openstep ufs,
actully this was darwin's ufs which has the same layout,
I just set s_dirblksize to right value, may be for
UFS_MOUNT_UFSTYPE_NEXTSTEP, UFS_MOUNT_UFSTYPE_NEXTSTEP_CD you need
do the same, see TODO items in fs/ufs/super.c.
--
/Evgeniy
next prev parent reply other threads:[~2007-11-22 4:19 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-20 20:29 Problem with ufs nextstep in 2.6.18 (debian) Dave Bailey
2007-11-21 15:37 ` Jan Kara
2007-11-22 4:19 ` Evgeniy Dushistov [this message]
-- strict thread matches above, loose matches on Subject: below --
2007-11-25 1:26 Dave Bailey
2007-04-16 7:32 Evgeniy Dushistov
2007-04-16 16:04 ` Dale Amon
2007-04-17 1:10 ` Dale Amon
2007-04-19 16:39 ` Dale Amon
2007-04-15 1:38 Dale Amon
2007-04-15 23:11 ` Dale Amon
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20071122041412.GB9896@rain \
--to=dushistov@mail.ru \
--cc=dsbailey@pacbell.net \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.