From: Andrew Morton <akpm@linux-foundation.org>
To: David Brownell <david-b@pacbell.net>
Cc: cebbert@redhat.com, linux-kernel@vger.kernel.org
Subject: Re: Two identical entries for "rtc" in /proc/devices
Date: Sat, 15 Sep 2007 22:10:15 -0700 [thread overview]
Message-ID: <20070915221015.02aad5ea.akpm@linux-foundation.org> (raw)
In-Reply-To: <20070915185020.16BB51F9EAA@adsl-69-226-248-13.dsl.pltn13.pacbell.net>
On Sat, 15 Sep 2007 11:50:21 -0700 David Brownell <david-b@pacbell.net> wrote:
> > On Thu, 06 Sep 2007 18:23:22 -0400 Chuck Ebbert <cebbert@redhat.com> wrote:
> >
> > > # ls -li
> > > total 0
> > > 4026532007 -r--r--r-- 1 root root 0 Sep 6 18:18 nvram
> > > 4026532067 -r--r--r-- 1 root root 0 Sep 6 18:18 rtc
> > > 4026532067 -r--r--r-- 1 root root 0 Sep 6 18:18 rtc
> > > 4026532056 -rw-r--r-- 1 root root 0 Sep 6 18:18 snd-page-alloc
> >
> > Next -mm has
> >
> > procfs-detect-duplicate-names.patch
> > procfs-detect-duplicate-names-fix.patch
> > procfs-detect-duplicate-names-fix-fix-2.patch
> >
> > which will at least tell us who the second offender is.
>
> Semes pretty clear that this must be procfs itself...
> when a filesystem sees a name in a directory, it should
> refuse to make another file with the same name. And it
> should *never* reuse inode numbers...
>
procfs can reject the attempt to create the file, but the bottom line
is that two different callsites are trying to create the same file. One
of those callsites needs fixing?
next prev parent reply other threads:[~2007-09-16 5:10 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-06 22:23 Two identical entries for "rtc" in /proc/devices Chuck Ebbert
2007-09-15 7:44 ` Andrew Morton
2007-09-15 18:50 ` David Brownell
2007-09-16 5:10 ` Andrew Morton [this message]
2007-09-19 5:21 ` 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=20070915221015.02aad5ea.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=cebbert@redhat.com \
--cc=david-b@pacbell.net \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox