On Tue, Nov 11, 2014 at 10:27:43PM +0200, Giedrius Statkevicius wrote: > Hello, > Since this commit: > > commit 32eca22180804f71b06b63fd29b72f58be8b3c47 > Author: Martin Kepplinger <mart...@posteo.de> > Date: Wed Oct 29 20:22:56 2014 +0100 > > misc: always assign miscdevice to file->private_data in open() > > As of now, a miscdevice driver has to provide an implementation of > the open() file operation if it wants to have misc_open() assign a > pointer to struct miscdevice to file->private_data for other file > operations to use (given the user calls open()). > > This leads to situations where a miscdevice driver that doesn't need > internal operations during open() has to implement open() that only > returns immediately, in order to use the data in private_data in other > fops. > > This provides consistent behaviour for miscdevice developers and will > always provide the pointer in private_data. A driver's open() fop would, > of course, just overwrite it, when using private_data itself. > > Signed-off-by: Martin Kepplinger <mart...@posteo.de> > Signed-off-by: Greg Kroah-Hartman <gre...@linuxfoundation.org> > > I've noticed that my computer freezes a lot and I'm not able to shutdown > (it just freezes while shutdowning and I have to use SysRq+reisub) and I > get these messages in my journal:
If you revert this patch, does things go back to "normal" for you? thanks, greg k-h -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
