1. 13 Aug, 2020 3 commits
    • Linus Torvalds's avatar
      Merge tag 'exfat-for-5.9-rc1' of git://git.kernel.org/pub/scm/linux/kernel/git/linkinjeon/exfat · ff419b61
      Linus Torvalds authored
      Pull exfat updates from Namjae Jeon:
      
       - don't clear MediaFailure and VolumeDirty bit in volume flags if these
         were already set before mounting
      
       - write multiple dirty buffers at once in sync mode
      
       - remove unneeded EXFAT_SB_DIRTY bit set
      
      * tag 'exfat-for-5.9-rc1' of git://git.kernel.org/pub/scm/linux/kernel/git/linkinjeon/exfat:
        exfat: retain 'VolumeFlags' properly
        exfat: optimize exfat_zeroed_cluster()
        exfat: add error check when updating dir-entries
        exfat: write multiple sectors at once
        exfat: remove EXFAT_SB_DIRTY flag
      ff419b61
    • Johannes Weiner's avatar
      mm: memcontrol: fix warning when allocating the root cgroup · 9f457179
      Johannes Weiner authored
      Commit 3e38e0aa ("mm: memcg: charge memcg percpu memory to the
      parent cgroup") adds memory tracking to the memcg kernel structures
      themselves to make cgroups liable for the memory they are consuming
      through the allocation of child groups (which can be significant).
      
      This code is a bit awkward as it's spread out through several functions:
      The outermost function does memalloc_use_memcg(parent) to set up
      current->active_memcg, which designates which cgroup to charge, and the
      inner functions pass GFP_ACCOUNT to request charging for specific
      allocations.  To make sure this dependency is satisfied at all times -
      to make sure we don't randomly charge whoever is calling the functions -
      the inner functions warn on !current->active_memcg.
      
      However, this triggers a false warning when the root memcg itself is
      allocated.  No parent exists in this case, and so current->active_memcg
      is rightfully NULL.  It's a false positive, not indicative of a bug.
      
      Delete the warnings for now, we can revisit this later.
      
      Fixes: 3e38e0aa ("mm: memcg: charge memcg percpu memory to the parent cgroup")
      Signed-off-by: default avatarJohannes Weiner <hannes@cmpxchg.org>
      Reported-by: default avatarStephen Rothwell <sfr@canb.auug.org.au>
      Acked-by: default avatarRoman Gushchin <guro@fb.com>
      Cc: Andrew Morton <akpm@linux-foundation.org>
      Signed-off-by: default avatarLinus Torvalds <torvalds@linux-foundation.org>
      9f457179
    • Linus Torvalds's avatar
      Merge tag 'rtc-5.9' of git://git.kernel.org/pub/scm/linux/kernel/git/abelloni/linux · dc06fe51
      Linus Torvalds authored
      Pull RTC updates from Alexandre Belloni:
       "Not much this cycle - mostly non urgent driver fixes:
      
         - ds1374: use watchdog core
      
         - pcf2127: add alarm and pcf2129 support"
      
      * tag 'rtc-5.9' of git://git.kernel.org/pub/scm/linux/kernel/git/abelloni/linux:
        rtc: pcf2127: fix alarm handling
        rtc: pcf2127: add alarm support
        rtc: pcf2127: add pca2129 device id
        rtc: max77686: Fix wake-ups for max77620
        rtc: ds1307: provide an indication that the watchdog has fired
        rtc: ds1374: remove unused define
        rtc: ds1374: fix RTC_DRV_DS1374_WDT dependencies
        rtc: cleanup obsolete comment about struct rtc_class_ops
        rtc: pl031: fix set_alarm by adding back call to alarm_irq_enable
        rtc: ds1374: wdt: Use watchdog core for watchdog part
        rtc: Replace HTTP links with HTTPS ones
        rtc: goldfish: Enable interrupt in set_alarm() when necessary
        rtc: max77686: Do not allow interrupt to fire before system resume
        rtc: imxdi: fix trivial typos
        rtc: cpcap: fix range
      dc06fe51
  2. 12 Aug, 2020 37 commits