mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Satyam Sharma <satyam@infradead.org>
To: Chris Rankin <rankincj@yahoo.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [BUG] Linux 2.6.22 - Atomic counter underflow in NFS
Date: Thu, 2 Aug 2007 03:07:58 +0530 (IST)	[thread overview]
Message-ID: <alpine.LFD.0.999.0708020302570.8258@enigma.security.iitk.ac.in> (raw)
In-Reply-To: <699754.45152.qm@web52901.mail.re2.yahoo.com>



On Wed, 1 Aug 2007, Chris Rankin wrote:

> --- Satyam Sharma <satyam@infradead.org> wrote:
> > I expect this is easy to reproduce at will (when shutting down nfs
> > services, probably), right?
> 
> I'm not sure about the "at will" part because this is the first time I've seen it since 2.6.22 was
> released. However, I was upgrading my Fedora 7 nfs-utils package at the time so it probably did
> happen when the NFS service was being shut down.

Hmm, the backtrace suggests it should be reproducible fairly frequently.

> > Please try the latest mainline -git kernel (say 2.6.23-rc1-git10 from
> > kernel.org) and let us know if this still occurs? There were some fixes
> > regarding sysfs symlink refcounting that went in recently, and this looks
> > like one of those cases to me.
> 
> Do you have the actual patches instead?

I was thinking maybe this one: http://lkml.org/lkml/diff/2007/7/18/48/1

The kref_put() there happens on the sysfs_remove_link() path, and the
patch above fixed an extra put() during create_link(), which lead to
the final put() during remove_link() being what causes this underflow.
However, a lot changed in sysfs in the past few months, and I'm not
really sure that patch would apply cleanly. Hence, if you can try with
the latest -git ...


Thanks,
Satyam

      reply	other threads:[~2007-08-01 21:25 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-08-01 17:45 Chris Rankin
2007-08-01 21:11 ` Satyam Sharma
2007-08-01 21:11   ` Chris Rankin
2007-08-01 21:37     ` Satyam Sharma [this message]

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=alpine.LFD.0.999.0708020302570.8258@enigma.security.iitk.ac.in \
    --to=satyam@infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rankincj@yahoo.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

all inboxes | Powered by JetHome®