From: Andrew Morton <akpm@linux-foundation.org>
To: Zhang Rui <rui.zhang@intel.com>
Cc: Oliver Neukum <oliver@neukum.org>,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-acpi@vger.kernel.org
Subject: Re: [PATCH] [-mm] FS: file name must be unique in the same dir in procfs
Date: Mon, 10 Sep 2007 00:49:27 -0700 [thread overview]
Message-ID: <20070910004927.323763ad.akpm@linux-foundation.org> (raw)
In-Reply-To: <1187625005.2920.167.camel@acpi-hp.sh.intel.com>
On Mon, 20 Aug 2007 23:50:05 +0800 Zhang Rui <rui.zhang@intel.com> wrote:
> Hi, Oliver,
> Thanks for your comments,
>
> On Mon, 2007-08-20 at 18:45 +0800, Oliver Neukum wrote:
> > Am Montag 20 August 2007 schrieb Zhang Rui:
> > > Files name must be unique in the same directory.
> > >
> > > Bug is reported here:
> > > http://bugzilla.kernel.org/show_bug.cgi?id=8798
> >
> > Then I'd say fix the callers.
> But at least the callers need to be told that something is wrong first.
>
> > This will paper over bugs.
> Hmm, what kind of bugs?
> callers always need to check the return value when calling
> proc_mkdir/create_proc_entry, don't they?
>
Yes, but there's some risk that such a change will cause a
presently-working system to stop working. It's quite likely, if that
system is checking the procfs-creation return value.
So I think it'd be best if we were to detect the duplication and print a
warning (which should include, if possible, the full pathname and a
dump_stack()) and then the code should proceed as normal: permit the
duplicated entry and return success.
Then, when such duplicates are reported, we can work out what to do about
them on a case-by-case basis.
(btw, please feed your patches through scripts/checkpatch.pl - that one had
a remarkably high coding-style-error-density).
next prev parent reply other threads:[~2007-09-10 7:50 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-20 10:28 [PATCH] [-mm] FS: file name must be unique in the same dir in procfs Zhang Rui
2007-08-20 10:45 ` Oliver Neukum
2007-08-20 15:50 ` Zhang Rui
2007-09-10 7:49 ` Andrew Morton [this message]
2007-09-11 6:43 ` Zhang Rui
2007-09-14 1:37 ` Andrew Morton
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=20070910004927.323763ad.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=oliver@neukum.org \
--cc=rui.zhang@intel.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;
as well as URLs for NNTP newsgroup(s).