mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Jörn Engel" <joern@wohnheim.fh-wedel.de>
To: Chris Wedgwood <cw@f00f.org>
Cc: Linus Torvalds <torvalds@osdl.org>,
	LKML <linux-kernel@vger.kernel.org>,
	viro@parcelfarce.linux.theplanet.co.uk
Subject: Re: [PATCH] stat nlink resolution fix
Date: Tue, 15 Jun 2004 16:56:25 +0200	[thread overview]
Message-ID: <20040615145624.GC20432@wohnheim.fh-wedel.de> (raw)
In-Reply-To: <20040615055507.GA9847@taniwha.stupidest.org>

On Mon, 14 June 2004 22:55:07 -0700, Chris Wedgwood wrote:
> 
> Some filesystems can get overflows when their link-count exceeds
> 65534.  This patch increases the kernels internal resolution for this
> and also has a check for the old-system call paths to return and error
> (-EOVERFLOW) as required (as suggested by Al Viro).
> 
> Signed-off-by: Chris Wedgwood <cw@f00f.org>
> 
> diff -Nru a/include/linux/stat.h b/include/linux/stat.h
> --- a/include/linux/stat.h	2004-06-14 17:40:21 -07:00
> +++ b/include/linux/stat.h	2004-06-14 17:40:21 -07:00
> @@ -60,7 +60,7 @@
>  	unsigned long	ino;
>  	dev_t		dev;
>  	umode_t		mode;
> -	nlink_t		nlink;
> +	unsigned int	nlink;
>  	uid_t		uid;
>  	gid_t		gid;
>  	dev_t		rdev;

Just for me to get a clue, what would break if the definition of
nlink_t changed?

Jörn

-- 
Fancy algorithms are buggier than simple ones, and they're much harder
to implement. Use simple algorithms as well as simple data structures.
-- Rob Pike

  reply	other threads:[~2004-06-15 14:56 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-06-15  5:55 Chris Wedgwood
2004-06-15 14:56 ` Jörn Engel [this message]
2004-06-15 18:20   ` Chris Wedgwood

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=20040615145624.GC20432@wohnheim.fh-wedel.de \
    --to=joern@wohnheim.fh-wedel.de \
    --cc=cw@f00f.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@osdl.org \
    --cc=viro@parcelfarce.linux.theplanet.co.uk \
    /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®