Skip to content
Snippets Groups Projects
  1. Jul 19, 2021
  2. Jul 18, 2021
  3. Jul 16, 2021
  4. Jul 14, 2021
    • Theodore Ts'o's avatar
      ext4: fix possible UAF when remounting r/o a mmp-protected file system · 7d7d26aa
      Theodore Ts'o authored
      mainline inclusion
      from mainline-5.14
      commit	61bb4a1c417e5b95d9edb4f887f131de32e419cb
      category: bugfix
      bugzilla: 173880
      CVE: NA
      
      -------------------------------------------------
      
      After commit 618f003199c6 ("ext4: fix memory leak in
      ext4_fill_super"), after the file system is remounted read-only, there
      is a race where the kmmpd thread can exit, causing sbi->s_mmp_tsk to
      point at freed memory, which the call to ext4_stop_mmpd() can trip
      over.
      
      Fix this by only allowing kmmpd() to exit when it is stopped via
      ext4_stop_mmpd().
      
      Link: https://lore.kernel.org/r/20210707002433.3719773-1-tytso@mit.edu
      
      
      Reported-by: default avatarYe Bin <yebin10@huawei.com>
      Bug-Report-Link: <20210629143603.2166962-1-yebin10@huawei.com>
      Signed-off-by: default avatarTheodore Ts'o <tytso@mit.edu>
      Reviewed-by: default avatarJan Kara <jack@suse.cz>
      
      Conflicts:
      	fs/ext4/super.c
      
      Signed-off-by: default avatarBaokun Li <libaokun1@huawei.com>
      Reviewed-by: default avatarZhang Yi <yi.zhang@huawei.com>
      Signed-off-by: Yang Yingliang <yangying...
      7d7d26aa
    • Luo Meng's avatar
      locks: Fix UBSAN undefined behaviour in flock64_to_posix_lock · 1b84bd6f
      Luo Meng authored
      mainline inclusion
      from mainline-v5.11-rc1
      commit 16238415eb9886328a89fe7a3cb0b88c7335fe16
      category: bugfix
      bugzilla: 38689
      CVE: NA
      
      -----------------------------------------------
      
      When the sum of fl->fl_start and l->l_len overflows,
      UBSAN shows the following warning:
      
      UBSAN: Undefined behaviour in fs/locks.c:482:29
      signed integer overflow: 2 + 9223372036854775806
      cannot be represented in type 'long long int'
      Call Trace:
       __dump_stack lib/dump_stack.c:77 [inline]
       dump_stack+0xe4/0x14e lib/dump_stack.c:118
       ubsan_epilogue+0xe/0x81 lib/ubsan.c:161
       handle_overflow+0x193/0x1e2 lib/ubsan.c:192
       flock64_to_posix_lock fs/locks.c:482 [inline]
       flock_to_posix_lock+0x595/0x690 fs/locks.c:515
       fcntl_setlk+0xf3/0xa90 fs/locks.c:2262
       do_fcntl+0x456/0xf60 fs/fcntl.c:387
       __do_sys_fcntl fs/fcntl.c:483 [inline]
       __se_sys_fcntl fs/fcntl.c:468 [inline]
       __x64_sys_fcntl+0x12d/0x180 fs/fcntl.c:468
       do_syscall_64+0xc8/0x5a0 arch/x86/entry/common.c:293
       entry_SY...
      1b84bd6f
    • Matthew Wilcox (Oracle)'s avatar
      iomap: Mark read blocks uptodate in write_begin · a259beb0
      Matthew Wilcox (Oracle) authored
      
      mainline inclusion
      from mainline-v5.10
      commit 14284fed
      category: bugfix
      bugzilla: 43547
      CVE: NA
      
      -----------------------------------------------
      
      When bringing (portions of) a page uptodate, we were marking blocks that
      were zeroed as being uptodate, but not blocks that were read from storage.
      
      Like the previous commit, this problem was found with generic/127 and
      a kernel which failed readahead I/Os.  This bug causes writes to be
      silently lost when working with flaky storage.
      
      Fixes: 9dc55f13 ("iomap: add support for sub-pagesize buffered I/O without buffer heads")
      Signed-off-by: default avatarMatthew Wilcox (Oracle) <willy@infradead.org>
      Reviewed-by: default avatarDarrick J. Wong <darrick.wong@oracle.com>
      Signed-off-by: default avatarDarrick J. Wong <darrick.wong@oracle.com>
      Reviewed-by: default avatarChristoph Hellwig <hch@lst.de>
      
      conflicts:
      fs/iomap.c
      
      Signed-off-by: default avatarYe Bin <yebin10@huawei.com>
      Reviewed-by: default avatarZhang Yi <yi.zhang@huawei.com>
      Signed-off-by: Yang Yingliang <yangyi...
      a259beb0
    • Matthew Wilcox (Oracle)'s avatar
      iomap: Clear page error before beginning a write · b3a0aab5
      Matthew Wilcox (Oracle) authored
      
      mainline inclusion
      from mainline-v5.10-rc1
      commit e6e7ca92
      category: bugfix
      bugzilla: 43551
      CVE: NA
      
      -----------------------------------------------
      
      If we find a page in write_begin which is !Uptodate, we need
      to clear any error on the page before starting to read data
      into it.  This matches how filemap_fault(), do_read_cache_page()
      and generic_file_buffered_read() handle PageError on !Uptodate pages.
      When calling iomap_set_range_uptodate() in __iomap_write_begin(), blocks
      were not being marked as uptodate.
      
      This was found with generic/127 and a specially modified kernel which
      would fail (some) readahead I/Os.  The test read some bytes in a prior
      page which caused readahead to extend into page 0x34.  There was
      a subsequent write to page 0x34, followed by a read to page 0x34.
      Because the blocks were still marked as !Uptodate, the read caused all
      blocks to be re-read, overwriting the write.  With this change, and the
      next one, the bytes which were written are marked as being Uptodate, so
      even though the page is still marked as !Uptodate, the blocks containing
      the written data are not re-read from storage.
      
      Fixes: 9dc55f13 ("iomap: add support for sub-pagesize buffered I/O without buffer heads")
      Signed-off-by: default avatarMatthew Wilcox (Oracle) <willy@infradead.org>
      Reviewed-by: default avatarDarrick J. Wong <darrick.wong@oracle.com>
      Signed-off-by: default avatarDarrick J. Wong <darrick.wong@oracle.com>
      Reviewed-by: default avatarChristoph Hellwig <hch@lst.de>
      
      conflicts:
      fs/iomap.c
      
      Signed-off-by: default avatarYe Bin <yebin10@huawei.com>
      Reviewed-by: default avatarZhang Yi <yi.zhang@huawei.com>
      Signed-off-by: default avatarYang Yingliang <yangyingliang@huawei.com>
      b3a0aab5
    • Christoph Hellwig's avatar
      iomap: move the zeroing case out of iomap_read_page_sync · 9fdbab15
      Christoph Hellwig authored
      
      mainline inclusion
      from mainline-v5.5-rc1
      commit d3b40439
      category: bugfix
      bugzilla: 43551
      CVE: NA
      
      -----------------------------------------------
      
      That keeps the function a little easier to understand, and easier to
      modify for pending enhancements.
      
      Signed-off-by: default avatarChristoph Hellwig <hch@lst.de>
      Reviewed-by: default avatarDarrick J. Wong <darrick.wong@oracle.com>
      Signed-off-by: default avatarDarrick J. Wong <darrick.wong@oracle.com>
      
      conflicts:
      fs/iomap.c
      
      Signed-off-by: default avatarYe Bin <yebin10@huawei.com>
      Reviewed-by: default avatarZhang Yi <yi.zhang@huawei.com>
      Signed-off-by: default avatarYang Yingliang <yangyingliang@huawei.com>
      9fdbab15
    • Josef Bacik's avatar
      nbd: handle device refs for DESTROY_ON_DISCONNECT properly · c72b1648
      Josef Bacik authored
      mainline inclusion
      from mainline-5.12-rc1
      commit c9a2f90f4d6b
      category: bugfix
      bugzilla: 50455
      CVE: NA
      
      -------------------------------------------------
      
      There exists a race where we can be attempting to create a new nbd
      configuration while a previous configuration is going down, both
      configured with DESTROY_ON_DISCONNECT.  Normally devices all have a
      reference of 1, as they won't be cleaned up until the module is torn
      down.  However with DESTROY_ON_DISCONNECT we'll make sure that there is
      only 1 reference (generally) on the device for the config itself, and
      then once the config is dropped, the device is torn down.
      
      The race that exists looks like this
      
      TASK1					TASK2
      nbd_genl_connect()
        idr_find()
          refcount_inc_not_zero(nbd)
            * count is 2 here ^^
      					nbd_config_put()
      					  nbd_put(nbd) (count is 1)
          setup new config
            check DESTROY_ON_DISCONNECT
      	put_dev = true
          if (put_dev) nbd_put(nbd)
      	* free'd here ^^
      
      In nbd_genl_conne...
      c72b1648
    • Paul Aurich's avatar
      cifs: Fix leak when handling lease break for cached root fid · 25ebc65f
      Paul Aurich authored
      mainline inclusion
      from mainline-5.9-rc1
      commit baf57b56
      category: bugfix
      bugzilla: 40791
      CVE: NA
      
      ---------------------------
      
      Handling a lease break for the cached root didn't free the
      smb2_lease_break_work allocation, resulting in a leak:
      
          unreferenced object 0xffff98383a5af480 (size 128):
            comm "cifsd", pid 684, jiffies 4294936606 (age 534.868s)
            hex dump (first 32 bytes):
              c0 ff ff ff 1f 00 00 00 88 f4 5a 3a 38 98 ff ff  ..........Z:8...
              88 f4 5a 3a 38 98 ff ff 80 88 d6 8a ff ff ff ff  ..Z:8...........
            backtrace:
              [<0000000068957336>] smb2_is_valid_oplock_break+0x1fa/0x8c0
              [<0000000073b70b9e>] cifs_demultiplex_thread+0x73d/0xcc0
              [<00000000905fa372>] kthread+0x11c/0x150
              [<0000000079378e4e>] ret_from_fork+0x22/0x30
      
      Avoid this leak by only allocating when necessary.
      
      Fixes: a93864d9 ("cifs: add lease tracking to the cached root fid")
      Signed-o...
      25ebc65f
  5. Jul 12, 2021