From: David Kleikamp <shaggy@austin.ibm.com>
To: marcelo@conectiva.com.br
Cc: linux-kernel@vger.kernel.org
Subject: [PATCH] Make in-kernel i_nlink field be unsigned int
Date: Thu, 5 Sep 2002 16:04:10 -0500 [thread overview]
Message-ID: <200209052104.g85L4A9d002084@kleikamp.austin.ibm.com> (raw)
Marcelo,
This is a backport of the fix Linus dropped into the 2.5 tree. Can you
put this into 2.4?
Linus' abstract:
> Make in-kernel inode 'nlink' field be "unsigned int" instead
> of something arch-dependent and usually less.
>
> We may want to do value limiting in generic_fillattr() if people
> end up caring.
Of course, 2.4 doesn't have generic_fillattr. This would be cp_old_stat
and cp_new_stat.
Thanks,
Shaggy
===== include/linux/fs.h 1.68 vs edited =====
--- 1.68/include/linux/fs.h Fri Aug 23 08:27:33 2002
+++ edited/include/linux/fs.h Thu Sep 5 15:33:33 2002
@@ -442,7 +442,7 @@
atomic_t i_count;
kdev_t i_dev;
umode_t i_mode;
- nlink_t i_nlink;
+ unsigned int i_nlink;
uid_t i_uid;
gid_t i_gid;
kdev_t i_rdev;
reply other threads:[~2002-09-05 20:59 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=200209052104.g85L4A9d002084@kleikamp.austin.ibm.com \
--to=shaggy@austin.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=marcelo@conectiva.com.br \
/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;
as well as URLs for NNTP newsgroup(s).