public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: David Brownell <david-b@pacbell.net>
To: linux-kernel@vger.kernel.org, Patrick Mochel <mochel@osdl.org>
Subject: 2.5.recent: device_remove_file() doesn't
Date: Wed, 26 Mar 2003 19:53:17 -0800	[thread overview]
Message-ID: <3E8275AD.40603@pacbell.net> (raw)

I've noticed that recent kernels don't clean up device
attribute files correctly when they're removed.  Instead,
they're left in the directory with a refcount of zero.

That refcount stays even when the file is recreated later;
and the contents can be read.  Delete them again, and now
the refcount is 65535 ... though now reading the contents
may cause oopsing.

This worked correctly at some point last month:  the file
no longer appeared in sysfs after deletion.

Got Patch?

- Dave



             reply	other threads:[~2003-03-27  3:31 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-03-27  3:53 David Brownell [this message]
2003-03-27 17:58 ` 2.5.recent: device_remove_file() doesn't Patrick Mochel
2003-03-27 20:04   ` Greg KH
2003-03-27 22:37     ` Mike Anderson
2003-03-27 23:34   ` David Brownell

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=3E8275AD.40603@pacbell.net \
    --to=david-b@pacbell.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mochel@osdl.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox