All of lore.kernel.org
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@infradead.org>
To: "Holger Hoffstätte" <holger@applied-asynchrony.com>
Cc: linux-block <linux-block@vger.kernel.org>
Subject: Re: Block device's sysfs setting getting lost after suspend-resume cycle
Date: Mon, 21 Apr 2025 04:49:11 -0700	[thread overview]
Message-ID: <aAYwtwV7KEQ-GSbi@infradead.org> (raw)
In-Reply-To: <32c5ca62-eeef-5fb5-51f5-80dac4effc98@applied-asynchrony.com>

On Sat, Apr 19, 2025 at 12:16:35PM +0200, Holger Hoffstätte wrote:
> I'm reasonably sure it used to retain the configured value.
> The same also happens with sd (SATA) devices on a different machine,
> so it seems to be a generic problem with either block or sysfs.
> 
> This is with 6.14.3-rc2. I have unfortunately no idea when this
> started to happen - i only noticed it now. Will trawl through
> git history but wanted to see if this rings a bell with someone.

I'm pretty sure this is the atomic queue limits series, and I'm
actually surprised it was persisted before as we don't have separated
hardware vs user limits.  I'll dig into it and get back to you ASAP
after catching up from having a few days off.


  reply	other threads:[~2025-04-21 11:49 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-04-19 10:16 Block device's sysfs setting getting lost after suspend-resume cycle Holger Hoffstätte
2025-04-21 11:49 ` Christoph Hellwig [this message]
2025-04-23  6:35 ` Christoph Hellwig
2025-04-23 10:11   ` Holger Hoffstätte
2025-04-23 16:19     ` Christoph Hellwig
2025-04-23 17:05       ` Holger Hoffstätte
2025-04-24  8:17         ` Christoph Hellwig

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=aAYwtwV7KEQ-GSbi@infradead.org \
    --to=hch@infradead.org \
    --cc=holger@applied-asynchrony.com \
    --cc=linux-block@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.