All of lore.kernel.org
 help / color / mirror / Atom feed
From: Massimiliano Hofer <max@bbs.cc.uniud.it>
To: linux-kernel@vger.kernel.org
Subject: Re: Kernel 2.6.14.2 - Hard link count is wrong
Date: Sun, 20 Nov 2005 19:27:42 +0100	[thread overview]
Message-ID: <200511201927.43430.max@bbs.cc.uniud.it> (raw)
In-Reply-To: <200511201614.09858.max@bbs.cc.uniud.it>

On Sunday 20 November 2005 4:14 pm, Massimiliano Hofer wrote:

> I'll write back as soon as possible with more tests.

I'm back. First of all I beg your pardon for blaming 2.6.14.2, I forgot I 
rebooted with 2.6.13.4.
A cursory check of the mailing list and the changelog doesn't show any obvious 
change in 2.6.14 that would solve this, but I may be overlooking something.

Anyway I couldn't reproduce the bug in 2.6.14.2, but it is easily reproducible 
with 2.6.13.4. Adding and removing a 8139too PCMCIA card I managed to get this 
warning:

find: WARNING: Hard link count (5) is wrong for /proc/bus/pci: this may be a 
bug in your filesystem driver.  Automatically turning on find's -noleaf 
option.  Earlier results may have failed to include directories that should 
have been searched.


Compiling pcmcia in the kernel (but leaving yenta and 8139too as a module) I 
never get errors on /proc/bus, but I get the same results on /proc/bus/pci.
It seems a broader hotplug problem. Of corse it could be already solved in 
2.6.14, as I can't reproduce it.

-- 
Bye,
   Massimiliano Hofer

  reply	other threads:[~2005-11-20 18:27 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-11-18 18:59 Kernel 2.6.14.2 - Hard link count is wrong Clemens Koller
2005-11-19  2:08 ` Daniel Drake
2005-11-20 14:41   ` Massimiliano Hofer
     [not found] ` <200511201522.35660.max@bbs.cc.uniud.it>
     [not found]   ` <4380914C.1010903@gentoo.org>
2005-11-20 15:14     ` Massimiliano Hofer
2005-11-20 18:27       ` Massimiliano Hofer [this message]
2005-11-21 11:17         ` Clemens Koller

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=200511201927.43430.max@bbs.cc.uniud.it \
    --to=max@bbs.cc.uniud.it \
    --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.