From: Andreas Schwab <schwab@suse.de>
To: Nikita Danilov <Nikita@Namesys.COM>
Cc: Petr Sebor <petr@scssoft.com>, linux-kernel@vger.kernel.org
Subject: Re: incorrect inode count on reiserfs
Date: Mon, 08 Dec 2003 15:11:09 +0100 [thread overview]
Message-ID: <jek757762q.fsf@sykes.suse.de> (raw)
In-Reply-To: <16340.33245.887082.96412@laputa.namesys.com> (Nikita Danilov's message of "Mon, 8 Dec 2003 16:51:25 +0300")
Nikita Danilov <Nikita@Namesys.COM> writes:
> inn2 should be fixed. :)
>
> Fix would really be simple: ignore test results if ->f_files is 0 or
> 0xffffffff.
That should better be (fsfilcnt_t)-1.
Andreas.
--
Andreas Schwab, SuSE Labs, schwab@suse.de
SuSE Linux AG, Maxfeldstraße 5, 90409 Nürnberg, Germany
Key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5
"And now for something completely different."
next prev parent reply other threads:[~2003-12-08 14:11 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-08 13:26 incorrect inode count on reiserfs Petr Sebor
2003-12-08 13:51 ` Nikita Danilov
2003-12-08 14:06 ` Petr Sebor
2003-12-08 14:11 ` Andreas Schwab [this message]
2003-12-08 14:35 ` Erik Hensema
2003-12-08 15:33 ` Nikita Danilov
2003-12-08 16:09 ` Matthias Urlichs
2003-12-08 17:24 ` Erik Hensema
2003-12-09 3:01 ` Herbert Poetzl
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=jek757762q.fsf@sykes.suse.de \
--to=schwab@suse.de \
--cc=Nikita@Namesys.COM \
--cc=linux-kernel@vger.kernel.org \
--cc=petr@scssoft.com \
/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