lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:	Sun, 15 Mar 2015 09:50:01 +0100
From:	Alexander Holler <holler@...oftware.de>
To:	Al Viro <viro@...IV.linux.org.uk>
CC:	Linus Torvalds <torvalds@...ux-foundation.org>,
	linux-kernel@...r.kernel.org, linux-fsdevel@...r.kernel.org,
	linux-usb@...r.kernel.org
Subject: Re: [git pull] gadgetfs fixes

Am 15.03.2015 um 09:17 schrieb Al Viro:

> Another question, if you don't mind - does that series (i.e. what's currently
> in Linus' tree) fix the module refcount issues you'd been seeing?  I agree
> with your analysis of likely cause (->f_op reassignments with different
> ->owner before and after) and these patches should have eliminated that, but
> confirmation would be nice...
>
> Incidentally, none of those file_operations need ->owner in the first place;
> it doesn't hurt (as long as ->f_op doesn't change that way), but such files
> (living on a filesystem provided by the module their methods are in)
> don't need the module refcount bumped while the file is opened - having it
> opened pins file_system_type of containing filesystem (by keeping a reference
> to struct vfsmount, which keeps a reference to struct super_block, which keeps
> a reference to file_system_type), so the module will be kept busy just fine.
> Again, having ->owner on file_operations doesn't hurt, so it's not a bug
> per se - just pointless in such cases.  So we might want to remove it
> from ep_io_operations someday.  Anyway, that's a completely separate story...

Hmm, a year ago or so I've stumbled over the fact that the owner might 
be necessary for correct entries in sysfs (that was mtd). I've no idea 
if that's true here too but it might be worse to mention it.

Alexander Holler
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ