All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Nicolai Stange <nicstange@gmail.com>
Cc: devel@driverdev.osuosl.org, linux-kernel@vger.kernel.org,
	"Arve Hjønnevåg" <arve@android.com>,
	"Riley Andrews" <riandrews@android.com>,
	"Gustavo Padovan" <gustavo.padovan@collabora.co.uk>
Subject: Re: [PATCH] staging/android: sync_debug: unproxify debugfs files' fops
Date: Fri, 27 May 2016 11:15:41 -0700	[thread overview]
Message-ID: <20160527181541.GA19224@kroah.com> (raw)
In-Reply-To: <1464372234-13431-1-git-send-email-nicstange@gmail.com>

On Fri, May 27, 2016 at 08:03:54PM +0200, Nicolai Stange wrote:
> Since commit 49d200deaa68 ("debugfs: prevent access to removed files'
> private data"), a debugfs file's file_operations methods get proxied
> through lifetime aware wrappers.
> 
> However, only a certain subset of the file_operations members is supported
> by debugfs and ->compat_ioctl isn't among them -- it appears to be NULL
> from the VFS layer's perspective.
> 
> This behaviour breaks the /sys/kernel/debug/sync/sw_sync file introduced
> concurrently with commit a44eb74cd413 ("staging/android: move SW_SYNC_USER
> to a debugfs file").
> 
> Since that file never gets removed, there is no file removal race and thus,
> a lifetime checking proxy isn't needed.
> 
> Avoid the proxying for /sys/kernel/debug/sync/sw_sync by creating it via
> debugfs_create_file_unsafe() rather than debugfs_create_file().
> For consistency, do the same for /sys/kernel/debug/sync/info.
> 
> Fixes: 49d200deaa68 ("debugfs: prevent access to removed files' private
>                       data")
> Fixes: a44eb74cd413 ("staging/android: move SW_SYNC_USER to a debugfs
>                       file")
> Signed-off-by: Nicolai Stange <nicstange@gmail.com>
> ---
>  Applicable to linux-next-20160527.
>  x86_64 allmodconfig build succeeds w/o any new warnings.
> 
>  Related discussion can be found here:
>  http://lkml.kernel.org/g/878tz22peb.fsf@gmail.com
> 
>  drivers/staging/android/sync_debug.c | 12 +++++++++---
>  1 file changed, 9 insertions(+), 3 deletions(-)

Thanks, will queue this up after 4.7-rc1 is out.

greg k-h

      reply	other threads:[~2016-05-27 18:15 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-05-27 18:03 [PATCH] staging/android: sync_debug: unproxify debugfs files' fops Nicolai Stange
2016-05-27 18:15 ` Greg Kroah-Hartman [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=20160527181541.GA19224@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=arve@android.com \
    --cc=devel@driverdev.osuosl.org \
    --cc=gustavo.padovan@collabora.co.uk \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nicstange@gmail.com \
    --cc=riandrews@android.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 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.