11 Apr, 2015

2 commits


09 Apr, 2015

1 commit


04 Apr, 2015

8 commits


27 Mar, 2015

2 commits


20 Mar, 2015

15 commits


28 Feb, 2015

5 commits

  • Documentation/memory-hotplug.txt describes that a callback function can
    be added to the notification chain by calling hotplug_memory_notifier().
    The function prototype of the callback function is mssing. This missing
    information is added by the patch.

    The description of the arguments of the callback function is
    reworked.

    The constants for the event types are corrected.

    The possible return values are explained.

    Signed-off-by: Heinrich Schuchardt
    Signed-off-by: Jonathan Corbet

    Heinrich Schuchardt
     
  • Try to make coding style documentation look a bit more readable and
    consistent with the following:

    - indent every code example in C to first tab-stop;
    - surround every code example with empty lines, both top and bottom;
    - remove empty lines where text looked way too spare;
    - do not indent examples in elisp and kconfig;
    - do not do any non-whitespace changes.

    Signed-off-by: Pavel Kretov
    Signed-off-by: Jonathan Corbet

    Pavel Kretov
     
  • Coding style description has a irregular mixture of tabs and spaces in two
    places which is bad by any means and can possibly hurt somebody's sense
    of beauty.

    Signed-off-by: Pavel Kretov
    Signed-off-by: Jonathan Corbet

    Pavel Kretov
     
  • Even "private" structure members need a leading "@" in their
    kernel-doc; otherwise, they will be treated as new section names in
    the resulting manual.

    Signed-off-by: Robert P. J. Day
    Acked-by: Randy Dunlap
    Acked-By: Sebastian Reichel
    Signed-off-by: Jonathan Corbet

    Robert P. J. Day
     
  • The documentation specified that a machine type is mandatory and made
    that assumption in a few places. However, for DT-only platforms, the
    current advice is that no machine type should be registered, so update
    accordingly.

    Signed-off-by: Gregory Fong
    Signed-off-by: Jonathan Corbet

    Gregory Fong
     

23 Feb, 2015

7 commits

  • .. after extensive statistical analysis of my G+ polling, I've come to
    the inescapable conclusion that internet polls are bad.

    Big surprise.

    But "Hurr durr I'ma sheep" trounced "I like online polls" by a 62-to-38%
    margin, in a poll that people weren't even supposed to participate in.
    Who can argue with solid numbers like that? 5,796 votes from people who
    can't even follow the most basic directions?

    In contrast, "v4.0" beat out "v3.20" by a slimmer margin of 56-to-44%,
    but with a total of 29,110 votes right now.

    Now, arguably, that vote spread is only about 3,200 votes, which is less
    than the almost six thousand votes that the "please ignore" poll got, so
    it could be considered noise.

    But hey, I asked, so I'll honor the votes.

    Linus Torvalds
     
  • Pull ext4 fixes from Ted Ts'o:
    "Ext4 bug fixes.

    We also reserved code points for encryption and read-only images (for
    which the implementation is mostly just the reserved code point for a
    read-only feature :-)"

    * tag 'ext4_for_linus' of git://git.kernel.org/pub/scm/linux/kernel/git/tytso/ext4:
    ext4: fix indirect punch hole corruption
    ext4: ignore journal checksum on remount; don't fail
    ext4: remove duplicate remount check for JOURNAL_CHECKSUM change
    ext4: fix mmap data corruption in nodelalloc mode when blocksize < pagesize
    ext4: support read-only images
    ext4: change to use setup_timer() instead of init_timer()
    ext4: reserve codepoints used by the ext4 encryption feature
    jbd2: complain about descriptor block checksum errors

    Linus Torvalds
     
  • Pull more vfs updates from Al Viro:
    "Assorted stuff from this cycle. The big ones here are multilayer
    overlayfs from Miklos and beginning of sorting ->d_inode accesses out
    from David"

    * 'for-linus-2' of git://git.kernel.org/pub/scm/linux/kernel/git/viro/vfs: (51 commits)
    autofs4 copy_dev_ioctl(): keep the value of ->size we'd used for allocation
    procfs: fix race between symlink removals and traversals
    debugfs: leave freeing a symlink body until inode eviction
    Documentation/filesystems/Locking: ->get_sb() is long gone
    trylock_super(): replacement for grab_super_passive()
    fanotify: Fix up scripted S_ISDIR/S_ISREG/S_ISLNK conversions
    Cachefiles: Fix up scripted S_ISDIR/S_ISREG/S_ISLNK conversions
    VFS: (Scripted) Convert S_ISLNK/DIR/REG(dentry->d_inode) to d_is_*(dentry)
    SELinux: Use d_is_positive() rather than testing dentry->d_inode
    Smack: Use d_is_positive() rather than testing dentry->d_inode
    TOMOYO: Use d_is_dir() rather than d_inode and S_ISDIR()
    Apparmor: Use d_is_positive/negative() rather than testing dentry->d_inode
    Apparmor: mediated_filesystem() should use dentry->d_sb not inode->i_sb
    VFS: Split DCACHE_FILE_TYPE into regular and special types
    VFS: Add a fallthrough flag for marking virtual dentries
    VFS: Add a whiteout dentry type
    VFS: Introduce inode-getting helpers for layered/unioned fs environments
    Infiniband: Fix potential NULL d_inode dereference
    posix_acl: fix reference leaks in posix_acl_create
    autofs4: Wrong format for printing dentry
    ...

    Linus Torvalds
     
  • Pull ARM fix from Russell King:
    "Just one fix this time around. __iommu_alloc_buffer() can cause a
    BUG() if dma_alloc_coherent() is called with either __GFP_DMA32 or
    __GFP_HIGHMEM set. The patch from Alexandre addresses this"

    * 'fixes' of git://ftp.arm.linux.org.uk/~rmk/linux-arm:
    ARM: 8305/1: DMA: Fix kzalloc flags in __iommu_alloc_buffer()

    Linus Torvalds
     
  • X-Coverup: just ask spender
    Cc: stable@vger.kernel.org
    Signed-off-by: Al Viro

    Al Viro
     
  • use_pde()/unuse_pde() in ->follow_link()/->put_link() resp.

    Cc: stable@vger.kernel.org
    Signed-off-by: Al Viro

    Al Viro
     
  • As it is, we have debugfs_remove() racing with symlink traversals.
    Supply ->evict_inode() and do freeing there - inode will remain
    pinned until we are done with the symlink body.

    And rip the idiocy with checking if dentry is positive right after
    we'd verified debugfs_positive(), which is a stronger check...

    Cc: stable@vger.kernel.org
    Signed-off-by: Al Viro

    Al Viro