Linux block layer
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Hardeep Sharma <quic_hardshar@quicinc.com>
Cc: Jens Axboe <axboe@kernel.dk>, Hannes Reinecke <hare@suse.de>,
	"Martin K . Petersen" <martin.petersen@oracle.com>,
	linux-block@vger.kernel.org, linux-kernel@vger.kernel.org,
	stable@vger.kernel.org
Subject: Re: [PATCH 6.6.y v2 1/1] block: Fix bounce check logic in blk_queue_may_bounce()
Date: Thu, 14 Aug 2025 11:03:51 +0200	[thread overview]
Message-ID: <2025081450-pacifist-laxative-bb4c@gregkh> (raw)
In-Reply-To: <20250814063655.1902688-1-quic_hardshar@quicinc.com>

On Thu, Aug 14, 2025 at 12:06:55PM +0530, Hardeep Sharma wrote:
> Buffer bouncing is needed only when memory exists above the lowmem region,
> i.e., when max_low_pfn < max_pfn. The previous check (max_low_pfn >=
> max_pfn) was inverted and prevented bouncing when it could actually be
> required.
> 
> Note that bouncing depends on CONFIG_HIGHMEM, which is typically enabled
> on 32-bit ARM where not all memory is permanently mapped into the kernel’s
> lowmem region.
> 
> Branch-Specific Note:
> 
> This fix is specific to this branch (6.6.y) only.
> In the upstream “tip” kernel, bounce buffer support for highmem pages
> was completely removed after kernel version 6.12. Therefore, this
> modification is not possible or relevant in the tip branch.
> 
> Fixes: 9bb33f24abbd0 ("block: refactor the bounce buffering code")
> Cc: stable@vger.kernel.org
> Signed-off-by: Hardeep Sharma <quic_hardshar@quicinc.com>

Why do you say this is only for 6.6.y, yet your Fixes: line is older
than that?

And why wasn't this ever found or noticed before?

Also, why can't we just remove all of the bounce buffering code in this
older kernel tree?  What is wrong with doing that instead?

And finally, how was this tested?

thanks,

greg k-h

  reply	other threads:[~2025-08-14  9:03 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-08-14  6:36 [PATCH 6.6.y v2 1/1] block: Fix bounce check logic in blk_queue_may_bounce() Hardeep Sharma
2025-08-14  9:03 ` Greg KH [this message]
2025-08-14 10:54   ` Hardeep Sharma
2025-08-14 11:36     ` Greg KH
2025-08-14 13:06       ` Hardeep Sharma
2025-08-14 13:54         ` Greg KH
2025-08-14 13:11       ` Hardeep Sharma
  -- strict thread matches above, loose matches on Subject: below --
2025-07-25 11:27 Hardeep Sharma
2025-07-25 12:04 ` 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=2025081450-pacifist-laxative-bb4c@gregkh \
    --to=gregkh@linuxfoundation.org \
    --cc=axboe@kernel.dk \
    --cc=hare@suse.de \
    --cc=linux-block@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=martin.petersen@oracle.com \
    --cc=quic_hardshar@quicinc.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