[lkml]   [2014]   [Nov]   [12]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: [PATCH] btrfs: Don't check for file->private_data on open(). It is set by the core.
Am 2014-11-12 um 18:59 schrieb Chris Mason:
> On Wed, Nov 12, 2014 at 11:38 AM, Martin Kepplinger <>
> wrote:
>> The miscdevice core now sets file->private_data to the struct miscdevice
>> so don't fail when this is not NULL.
>> Signed-off-by: Martin Kepplinger <>
>> ---
>> This is a question: what does this check provide and does overwriting
>> file->private_data make any difference?
>> Is miscdevice's open() by the user not allowed here, if
>> file->private_data
>> is set?
>> thanks!!
> Btrfs uses this in the transaction start ioctl to record the transaction
> handle being started. Ceph is the main user of the ioctl, and we could
> setup a hash table if needed. But which call path in miscdevice is
> doing this?
> With your patch in place, btrfs would end up overwriting the miscdevice
> private_data field, which would probably cause problems.
> -chris

I think i was mistaken, sorry. misc_open() used to set
file->private_data _only_ if you use set .open in struct file_operations.

In current -next this changed and file->private_data is set to struct
miscdevice on a (userspace's) open call (misc_open()) just in any case.

You do set .open so this wouldn't affect you and this patch can be ignored.


 \ /
  Last update: 2014-11-12 20:21    [W:0.034 / U:13.684 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site