1. 09 1月, 2012 1 次提交
    • A
      functionfs: unfuck failure exits on mount · 5b5f9560
      Al Viro 提交于
      * if you do dput() of root dentry, do *not* follow that with iput() of root
      inode.
      * while we are at it, don't do that dput() at all - you are leaving the pointer
      in ->s_root and your ->kill_sb() will be very unhappy with that.  It will do
      proper dput(), though, so the easiest way is to leave that to it entirely.
      * freeing ->s_fs_info is also best left to ->kill_sb() (which will do it
      anyway), especially since we leave the pointer in place.
      * that xchg() in ->kill_sb() is not a bug per se, but it's a plain and simple
      masturbation with fewer excuses than Onan had...
      Signed-off-by: NAl Viro <viro@zeniv.linux.org.uk>
      5b5f9560
  2. 12 12月, 2011 1 次提交
  3. 01 11月, 2011 1 次提交
  4. 10 9月, 2011 1 次提交
    • K
      usb gadget: clean up FSF boilerplate text · 28c9fc68
      Klaus Schwarzkopf 提交于
      remove the following two paragraphs as they are not needed:
      
      This program is distributed in the hope that it will be useful, but
      WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or
      FITNESS FOR A PARTICULAR PURPOSE.  See the GNU General Public
      License for more details.
      
      You should have received a copy of the GNU General Public License along with
      this program; if not, write to the Free Software Foundation, Inc.,59
      Temple Place - Suite 330, Boston, MA  02111-1307, USA.
      Signed-off-by: NKlaus Schwarzkopf <schwarzkopf@sensortherm.de>
      Signed-off-by: NGreg Kroah-Hartman <gregkh@suse.de>
      28c9fc68
  5. 29 6月, 2011 1 次提交
  6. 05 2月, 2011 1 次提交
  7. 11 12月, 2010 1 次提交
  8. 18 11月, 2010 2 次提交
  9. 17 11月, 2010 3 次提交
  10. 29 10月, 2010 1 次提交
  11. 27 10月, 2010 1 次提交
  12. 26 10月, 2010 1 次提交
    • C
      fs: do not assign default i_ino in new_inode · 85fe4025
      Christoph Hellwig 提交于
      Instead of always assigning an increasing inode number in new_inode
      move the call to assign it into those callers that actually need it.
      For now callers that need it is estimated conservatively, that is
      the call is added to all filesystems that do not assign an i_ino
      by themselves.  For a few more filesystems we can avoid assigning
      any inode number given that they aren't user visible, and for others
      it could be done lazily when an inode number is actually needed,
      but that's left for later patches.
      Signed-off-by: NChristoph Hellwig <hch@lst.de>
      Signed-off-by: NDave Chinner <dchinner@redhat.com>
      Signed-off-by: NAl Viro <viro@zeniv.linux.org.uk>
      85fe4025
  13. 11 8月, 2010 3 次提交
  14. 22 7月, 2010 1 次提交
  15. 21 5月, 2010 2 次提交
    • R
      USB: gadget: f_fs.c needs to include pagemap.h · b0608690
      Randy Dunlap 提交于
      Fix g_ffs build error, add a needed header file:
      
      drivers/usb/gadget/f_fs.c:1064:error: 'PAGE_CACHE_SIZE' undeclared (first use in this function)
      drivers/usb/gadget/f_fs.c:1065:error: 'PAGE_CACHE_SHIFT' undeclared (first use in this function)
      Signed-off-by: NRandy Dunlap <randy.dunlap@oracle.com>
      Acked-by: NMichał Nazarewicz <m.nazarewicz@samsung.com>
      Signed-off-by: NGreg Kroah-Hartman <gregkh@suse.de>
      b0608690
    • M
      USB: f_fs: the FunctionFS driver · ddf8abd2
      Michal Nazarewicz 提交于
      The FunctionFS is a USB composite function that can be used
      with the composite framework to create an USB gadget.
      
      >From kernel point of view it is just a composite function with
      some unique behaviour.  It may be added to an USB
      configuration only after the user space driver has registered
      by writing descriptors and strings (the user space program has
      to provide the same information that kernel level composite
      functions provide when they are added to the configuration).
      
      >From user space point of view it is a file system which when
      mounted provide an "ep0" file.  User space driver need to
      write descriptors and strings to that file.  It does not need
      to worry about endpoints, interfaces or strings numbers but
      simply provide descriptors such as if the function was the
      only one (endpoints and strings numbers starting from one and
      interface numbers starting from core).  The FunctionFS changes
      numbers of those as needed also handling situation when
      numbers differ in different configurations.
      
      When descriptors and strings are written "ep#" files appear
      (one for each declared endpoint) which handle communication on
      a single endpoint.  Again, FunctionFS takes care of the real
      numbers and changing of the configuration (which means that
      "ep1" file may be really mapped to (say) endpoint 3 (and when
      configuration changes to (say) endpoint 2)).  "ep0" is used
      for receiving events and handling setup requests.
      
      When all files are closed the function disables itself.
      Signed-off-by: NMichal Nazarewicz <m.nazarewicz@samsung.com>
      Cc: Kyungmin Park <kyungmin.park@samsung.com>
      Cc: Marek Szyprowski <m.szyprowski@samsung.com>
      Signed-off-by: NGreg Kroah-Hartman <gregkh@suse.de>
      ddf8abd2