linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Alexander Holler <holler@ahsoftware.de>
To: Al Viro <viro@ZenIV.linux.org.uk>
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 09:50:01 +0100	[thread overview]
Message-ID: <550547B9.1040602@ahsoftware.de> (raw)
In-Reply-To: <20150315081733.GV29656@ZenIV.linux.org.uk>

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

  parent reply	other threads:[~2015-03-15  8:50 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
     [not found]     ` <20150315013948.GU29656-3bDd1+5oDREiFSDQTTA3OLVCufUGDwFn@public.gmane.org>
2015-03-15  6:35       ` Alexander Holler
2015-03-15  8:17         ` Al Viro
2015-03-15  8:31           ` Alexander Holler
2015-03-16 10:11             ` Alexander Holler
2015-03-15  8:50           ` Alexander Holler [this message]
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=550547B9.1040602@ahsoftware.de \
    --to=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 \
    --cc=viro@ZenIV.linux.org.uk \
    /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;
as well as URLs for NNTP newsgroup(s).