All of lore.kernel.org
 help / color / mirror / Atom feed
From: "gregkh@linuxfoundation.org" <gregkh@linuxfoundation.org>
To: Matthias Schiffer <mschiffer@universe-factory.net>
Cc: Lisa Du <cldu@marvell.com>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: A race condition between debugfs and seq_file operation
Date: Wed, 10 Jun 2015 07:49:28 -0700	[thread overview]
Message-ID: <20150610144928.GA30851@kroah.com> (raw)
In-Reply-To: <55784305.4040309@universe-factory.net>

On Wed, Jun 10, 2015 at 04:00:37PM +0200, Matthias Schiffer wrote:
> On 06/10/2015 07:20 AM, gregkh@linuxfoundation.org wrote:
> > On Wed, Jun 10, 2015 at 05:00:03AM +0000, Lisa Du wrote:
> >>> -----Original Message-----
> >>> From: gregkh@linuxfoundation.org [mailto:gregkh@linuxfoundation.org]
> >>> Sent: 2015年6月10日 5:12
> >>> To: Lisa Du
> >>> Cc: linux-kernel@vger.kernel.org
> >>> Subject: Re: A race condition between debugfs and seq_file operation
> >>>
> >>> On Mon, Jun 08, 2015 at 04:28:10AM +0000, Lisa Du wrote:
> >>>> Hi, All
> >>>> Recently I met one race condition related to debugfs.
> >>>>
> >>>> Take an example from ion.c in kernel3.14:
> >>>> static int ion_debug_client_open(struct inode *inode, struct file
> >>>> *file) {
> >>>> 	return single_open(file, ion_debug_client_show, inode->i_private); }
> >>>>
> >>>> static const struct file_operations debug_client_fops = {
> >>>> 	.open = ion_debug_client_open,
> >>>> 	.read = seq_read,
> >>>> 	.llseek = seq_lseek,
> >>>> 	.release = single_release,
> >>>> };
> >>>> client->debug_root = debugfs_create_file(client->display_name, 0664,
> >>>> 					dev->clients_debug_root,
> >>>> 					client, &debug_client_fops);
> >>>>
> >>>> I find during I read the debugfs node, driver can do
> >>>> debugfs_remove_recursive(dentry); Is it expected?
> >>>
> >>> Yes.  Well, not "expected", but a mess, yes.
> >>>
> >>> Removing debugfs files are known to have lots of races, this isn't the only
> >>> one :(
> >> Thanks for the reply! 
> >> Not sure if there is any plan to resolve such races in the future?
> > 
> > Yes, I have "plans", but it's on my very long todo list behind lots of
> > other things...
> > 
> > If you want to look into it, please, that would be wonderful.
> > 
> > thanks,
> > 
> > greg k-h
> 
> I've stumbled across related issues a few days ago (mostly in network
> drivers). What I've found out:

<snip>

Yes, all of these are issues, as I mentioned.

greg k-h

      reply	other threads:[~2015-06-10 14:49 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CAG9bXvm70+hE5qsk1UGCzXn3d6FcDs1AJhjM-Homcsu2OmHt6w@mail.gmail.com>
     [not found] ` <CAG9bXv=xFZfuX26OXA+5Go38+JXbq-rwbhcjnyKdTacerRtCvA@mail.gmail.com>
     [not found]   ` <CAG9bXvnTPkD8ZDKNakqzKVuJ+iOETdYj6=R2moTnmdUP=X1YVw@mail.gmail.com>
2015-06-08  4:28     ` A race condition between debugfs and seq_file operation Lisa Du
2015-06-09 21:12       ` gregkh
2015-06-10  5:00         ` Lisa Du
2015-06-10  5:20           ` gregkh
2015-06-10  6:18             ` Lisa Du
2015-06-10 14:00             ` Matthias Schiffer
2015-06-10 14:49               ` gregkh [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=20150610144928.GA30851@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=cldu@marvell.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mschiffer@universe-factory.net \
    /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.