public inbox for linux-mm@kvack.org
 help / color / mirror / Atom feed
From: Sergey Senozhatsky <senozhatsky@chromium.org>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Sergey Senozhatsky <senozhatsky@chromium.org>,
	 Minchan Kim <minchan@kernel.org>,
	Brian Geffon <bgeffon@google.com>,
	linux-block@vger.kernel.org,  linux-mm@kvack.org,
	Qu Wenruo <wqu@suse.com>, Avinesh Kumar <avinesh.kumar@suse.com>,
	 Christoph Hellwig <hch@lst.de>
Subject: Re: [PATCH v3] zram: do not forget to endio for partial discard requests
Date: Wed, 1 Apr 2026 10:10:12 +0900	[thread overview]
Message-ID: <acxwQXhma2s-e7dF@google.com> (raw)
In-Reply-To: <20260331174926.58ef8dc4d40ac12f8ce3905d@linux-foundation.org>

On (26/03/31 17:49), Andrew Morton wrote:
> On Tue, 31 Mar 2026 16:42:44 +0900 Sergey Senozhatsky <senozhatsky@chromium.org> wrote:
> 
> > As reported by Qu Wenruo, the following
> > 
> >  getconf PAGESIZE
> >  65536
> >  blkdiscard -p 4k /dev/zram0
> > 
> > takes literally forever to complete.
> 
> I'm wondering how you measured this interval ;)

:)

> > zram doesn't support
> > partial discards and just returns immediately w/o doing any
> > discard work in such cases.  The problem is that we forget
> > to endio on our way out, so blkdiscard sleeps forever in
> > submit_bio_wait().  Fix this by jumping to end_bio label,
> > which does bio_endio().
> > 
> > Fixes: 0120dd6e4e202 ("zram: make zram_bio_discard more self-contained")
> > Signed-off-by: Sergey Senozhatsky <senozhatsky@chromium.org>
> > Reported-by: Qu Wenruo <wqu@suse.com>
> > Closes: https://lore.kernel.org/linux-block/92361cd3-fb8b-482e-bc89-15ff1acb9a59@suse.com
> > Test-by: Qu Wenruo <wqu@suse.com>
> > Cc: Avinesh Kumar <avinesh.kumar@suse.com>
> > Cc: Christoph Hellwig <hch@lst.de>
> 
> Thanks.  I made several changes to the changelog from the earlier
> discussion (Anivesh Reported-by:/Closes:) and added a cc:stable.

Thank you, sir!

> 
> 0120dd6e4e202 was a few years ago so no need to rush this into mainline
> - target this to the upcoming merge window.

Sounds good to me.


      reply	other threads:[~2026-04-01  1:10 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-31  7:42 [PATCH v3] zram: do not forget to endio for partial discard requests Sergey Senozhatsky
2026-03-31 15:07 ` Christoph Hellwig
2026-04-01  0:49 ` Andrew Morton
2026-04-01  1:10   ` Sergey Senozhatsky [this message]

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=acxwQXhma2s-e7dF@google.com \
    --to=senozhatsky@chromium.org \
    --cc=akpm@linux-foundation.org \
    --cc=avinesh.kumar@suse.com \
    --cc=bgeffon@google.com \
    --cc=hch@lst.de \
    --cc=linux-block@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=minchan@kernel.org \
    --cc=wqu@suse.com \
    /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