Linux s390 Architecture development
 help / color / mirror / Atom feed
From: Heiko Carstens <hca@linux.ibm.com>
To: Gerald Schaefer <gerald.schaefer@linux.ibm.com>
Cc: linux-s390 <linux-s390@vger.kernel.org>,
	Alexander Gordeev <agordeev@linux.ibm.com>,
	Vasily Gorbik <gor@linux.ibm.com>,
	Sven Schnelle <svens@linux.ibm.com>,
	Christian Borntraeger <borntraeger@linux.ibm.com>
Subject: Re: [PATCH] s390/appldata: Fix error handling in appldata_generic_handler()
Date: Wed, 21 Oct 2026 15:16:08 +0200	[thread overview]
Message-ID: <20261021131608.10194A44-hca@linux.ibm.com> (raw)
In-Reply-To: <20261021120426.1148360-1-gerald.schaefer@linux.ibm.com>

On Wed, Oct 21, 2026 at 02:04:26PM +0200, Gerald Schaefer wrote:
> appldata_generic_handler() always returns 0 after starting or stopping
> monitor recording.
> 
> So "echo {0,1} > /proc/sys/appldata/{os,mem,net_sum}" returns success even
> when DIAG 0xDC failed. A failed start would keep ops->active as 0, so
> reading the sysctl later would correctly reflect this.
> 
> A failed stop would falsely set ops->active to 0 and decrement module
> refcount. This would allow the data gathering module to be removed, and
> the data buffer to be freed, while z/VM monitor service is still collecting
> data from that buffer.
> 
> Fix this by returning -EIO when appldata_diag() failed, and only set
> ops->active to 0 and decrement module refcount when it succeeded on stop
> path.
> 
> Cc: stable@vger.kernel.org
> Signed-off-by: Gerald Schaefer <gerald.schaefer@linux.ibm.com>
> ---
>  arch/s390/appldata/appldata_base.c | 12 ++++++++----
>  1 file changed, 8 insertions(+), 4 deletions(-)

Applied, thanks!

      parent reply	other threads:[~2026-10-21 13:16 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-21 12:04 [PATCH] s390/appldata: Fix error handling in appldata_generic_handler() Gerald Schaefer
2026-10-21 12:07 ` sashiko-bot
2026-10-21 13:16 ` Heiko Carstens [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=20261021131608.10194A44-hca@linux.ibm.com \
    --to=hca@linux.ibm.com \
    --cc=agordeev@linux.ibm.com \
    --cc=borntraeger@linux.ibm.com \
    --cc=gerald.schaefer@linux.ibm.com \
    --cc=gor@linux.ibm.com \
    --cc=linux-s390@vger.kernel.org \
    --cc=svens@linux.ibm.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