diff options
| author | Martin Kepplinger <martink@posteo.de> | 2015-03-24 11:51:20 +1030 |
|---|---|---|
| committer | Rusty Russell <rusty@rustcorp.com.au> | 2015-03-24 11:52:06 +1030 |
| commit | 67c50bf292c1c02ec7ca548049c53cc08dc75ed1 (patch) | |
| tree | d3cd468c7f7a2d7a727f983b7b25b652dabd9d60 /lib/decompress_bunzip2.c | |
| parent | 88ad1a147e2c84d33cb50f5ebff1ece5e0cd4383 (diff) | |
| download | talos-op-linux-67c50bf292c1c02ec7ca548049c53cc08dc75ed1.tar.gz talos-op-linux-67c50bf292c1c02ec7ca548049c53cc08dc75ed1.zip | |
lguest: explicitly set miscdevice's private_data NULL
There is a proposed change to the miscdevice's behaviour on open(). Currently
file->private_data stays NULL, but only because we don't have an open-entry in
struct file_operations.
This may change so that private_data, more consistently, is always set to
struct miscdevice, not only *if* the driver has it's own open() routine and
fops-entry, see https://lkml.org/lkml/2014/12/4/939 and commit
94e4fe2cab3d43b3ba7c3f721743006a8c9d913a
In short: If we rely on file->private_data being NULL, we should ensure
it is NULL ourselves.
Signed-off-by: Martin Kepplinger <martink@posteo.de>
Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
Diffstat (limited to 'lib/decompress_bunzip2.c')
0 files changed, 0 insertions, 0 deletions
