From: Christoph Hellwig <hch@caldera.de>
To: Andries.Brouwer@cwi.nl
Cc: alan@lxorguk.ukuu.org.uk, hch@caldera.de, torvalds@transmeta.com,
viro@math.psu.edu, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] vxfs fix
Date: Wed, 1 Aug 2001 23:18:55 +0200 [thread overview]
Message-ID: <20010801231855.A16333@caldera.de> (raw)
In-Reply-To: <200108012103.VAA93890@vlet.cwi.nl>
In-Reply-To: <200108012103.VAA93890@vlet.cwi.nl>; from Andries.Brouwer@cwi.nl on Wed, Aug 01, 2001 at 09:03:20PM +0000
On Wed, Aug 01, 2001 at 09:03:20PM +0000, Andries.Brouwer@cwi.nl wrote:
> Dear Linus, Alan, Al, Christoph, all,
>
> If one mounts without specifying a type, mount will try
> all available types. After having tried vxfs the next type
> will cause
> set_blocksize: b_count 1 ...
> since vxfs forgets to free a block.
> The patch below adds the missing brelse().
> (In fact there are more resources that are never freed there -
> maybe the maintainer can have a look some time -
> I only added a comment.)
Yes, I already hit that one time but forgot to fix it.
I'll update vxfs to free all resources somewhen later this week.
Thanks for the catch!
> When mount continues to try all types, it may try V7.
> That always succeeds, there is no test for magic or so,
> and after garbage has been mounted as a V7 filesystem,
> the kernel crashes or hangs or fails in other sad ways.
> Have not tried to debug.
Maybe some sanity checks should be added?
I'd like to propose:
s_nfree <= V7_NICFREE
s_ninode <= V7_NICINOD
s_time != 0
Christoph
--
Of course it doesn't work. We've performed a software upgrade.
next prev parent reply other threads:[~2001-08-01 21:22 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-08-01 21:03 Andries.Brouwer
2001-08-01 21:18 ` Christoph Hellwig [this message]
2001-08-01 21:19 ` Alexander Viro
2001-08-01 22:29 ` Linus Torvalds
2001-08-02 0:15 ` Alan Cox
2001-08-02 19:15 Andries.Brouwer
[not found] <no.id>
2001-08-02 19:41 ` Alan Cox
2001-08-02 20:57 ` Andreas Dilger
2001-08-02 20:25 Andries.Brouwer
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=20010801231855.A16333@caldera.de \
--to=hch@caldera.de \
--cc=Andries.Brouwer@cwi.nl \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@transmeta.com \
--cc=viro@math.psu.edu \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®