public inbox for stable@vger.kernel.org
 help / color / mirror / Atom feed
From: Sasha Levin <sashal@kernel.org>
To: stable@vger.kernel.org
Cc: David Sterba <dsterba@suse.com>, Sasha Levin <sashal@kernel.org>
Subject: Re: [PATCH 6.6.x] btrfs: add cancellation points to trim loops
Date: Fri,  6 Dec 2024 18:11:54 -0500	[thread overview]
Message-ID: <20241206123447-20afebe2d14f0ae3@stable.kernel.org> (raw)
In-Reply-To: <20241206160134.17747-1-dsterba@suse.com>

[ Sasha's backport helper bot ]

Hi,

The upstream commit SHA1 provided is correct: 69313850dce33ce8c24b38576a279421f4c60996

WARNING: Author mismatch between patch and upstream commit:
Backport author: David Sterba <dsterba@suse.com>
Commit author: Luca Stefani <luca.stefani.ge1@gmail.com>


Status in newer kernel trees:
6.12.y | Present (exact SHA1)
6.6.y | Not found

Note: The patch differs from the upstream commit:
---
1:  69313850dce33 ! 1:  949c2e944f056 btrfs: add cancellation points to trim loops
    @@ Metadata
      ## Commit message ##
         btrfs: add cancellation points to trim loops
     
    +    commit 69313850dce33ce8c24b38576a279421f4c60996 upstream.
    +
         There are reports that system cannot suspend due to running trim because
         the task responsible for trimming the device isn't able to finish in
         time, especially since we have a free extent discarding phase, which can
    @@ fs/btrfs/free-space-cache.c: static int trim_bitmaps(struct btrfs_block_group *b
     
      ## fs/btrfs/free-space-cache.h ##
     @@
    - #include <linux/list.h>
    - #include <linux/spinlock.h>
    - #include <linux/mutex.h>
    -+#include <linux/freezer.h>
    - #include "fs.h"
    + #ifndef BTRFS_FREE_SPACE_CACHE_H
    + #define BTRFS_FREE_SPACE_CACHE_H
      
    - struct inode;
    ++#include <linux/freezer.h>
    ++
    + /*
    +  * This is the trim state of an extent or bitmap.
    +  *
     @@ fs/btrfs/free-space-cache.h: static inline bool btrfs_free_space_trimming_bitmap(
      	return (info->trim_state == BTRFS_TRIM_STATE_TRIMMING);
      }
---

Results of testing on various branches:

| Branch                    | Patch Apply | Build Test |
|---------------------------|-------------|------------|
| stable/linux-6.6.y        |  Success    |  Success   |

  reply	other threads:[~2024-12-06 23:11 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-12-06 16:01 [PATCH 6.6.x] btrfs: add cancellation points to trim loops David Sterba
2024-12-06 23:11 ` Sasha Levin [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-11-25 18:07 David Sterba
2024-11-25 18:14 ` kernel test robot
2024-11-25 18:59 ` Sasha Levin
2024-12-02 11:15 ` Greg KH
2024-12-03 15:27   ` David Sterba
2024-12-03 15:41     ` David Sterba
2024-12-06 12:37       ` Greg KH

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=20241206123447-20afebe2d14f0ae3@stable.kernel.org \
    --to=sashal@kernel.org \
    --cc=dsterba@suse.com \
    --cc=stable@vger.kernel.org \
    /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