From: Al Viro <viro@ZenIV.linux.org.uk>
To: Alexander Holler <holler@ahsoftware.de>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org,
linux-usb@vger.kernel.org
Subject: Re: [git pull] gadgetfs fixes
Date: Sun, 15 Mar 2015 08:17:34 +0000 [thread overview]
Message-ID: <20150315081733.GV29656@ZenIV.linux.org.uk> (raw)
In-Reply-To: <55052828.7090701@ahsoftware.de>
On Sun, Mar 15, 2015 at 07:35:20AM +0100, Alexander Holler wrote:
> > Umm... If I'm not misparsing what you said, you are talking about the
>
> Glücklicherweise nicht. Vielleicht sollten wir es zur Abwechslung mal
> mit meiner bevorzugten Sprache versuchen.
Good. I'll probably abstain from trying to mangle it, though.
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...
next prev parent reply other threads:[~2015-03-15 8:17 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-13 16:42 [git pull] gadgetfs fixes Al Viro
2015-03-15 0:39 ` Alexander Holler
2015-03-15 1:39 ` Al Viro
2015-03-15 6:35 ` Alexander Holler
2015-03-15 8:17 ` Al Viro [this message]
2015-03-15 8:31 ` Alexander Holler
2015-03-16 10:11 ` Alexander Holler
2015-03-15 8:50 ` Alexander Holler
2015-03-15 9:09 ` Al Viro
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=20150315081733.GV29656@ZenIV.linux.org.uk \
--to=viro@zeniv.linux.org.uk \
--cc=holler@ahsoftware.de \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=torvalds@linux-foundation.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox