All of lore.kernel.org
 help / color / mirror / Atom feed
From: Heiko Carstens <hca@linux.ibm.com>
To: Tristan Madani <tristmd@gmail.com>
Cc: Vasily Gorbik <gor@linux.ibm.com>,
	linux-s390@vger.kernel.org, stable@vger.kernel.org,
	Tristan Madani <tristan@talencesecurity.com>,
	Jan Hoeppner <hoeppner@linux.ibm.com>,
	Alexander Gordeev <agordeev@linux.ibm.com>
Subject: Re: [PATCH v2] s390/tape: cancel delayed work on device removal
Date: Tue, 20 Oct 2026 17:44:24 +0200	[thread overview]
Message-ID: <20261020154424.11179A48-hca@linux.ibm.com> (raw)
In-Reply-To: <20261019225606.1864082-1-tristmd@gmail.com>

Jan, this is for you, I would guess.

[full quote below]

On Mon, Oct 19, 2026 at 10:56:06PM +0000, Tristan Madani wrote:
> From: Tristan Madani <tristan@talencesecurity.com>
> 
> tape_generic_remove() drops the device reference without cancelling
> the pending delayed work tape_dnr. If tape_delayed_next_request() is
> still scheduled or running when the struct is freed on the final
> reference drop, the work function dereferences freed memory.
> 
> The cancel cannot go in tape_put_device() because that function is
> called from atomic context (under get_ccwdev_lock with interrupts
> disabled) and from within the work function itself, both of which
> would deadlock or sleep in atomic context with cancel_delayed_work_sync().
> 
> Add cancel_delayed_work_sync() in tape_generic_remove() after
> dev_set_drvdata() clears the device pointer and before dropping the
> final reference. At this point the spinlock is not held and the device
> is no longer reachable for new operations.
> 
> Fixes: 4111796d89b8c ("[PATCH] s390: channel tape fixes")
> Cc: stable@vger.kernel.org
> Signed-off-by: Tristan Madani <tristan@talencesecurity.com>
> ---
> Changes in v2:
> - Moved cancel from tape_put_device() to tape_generic_remove().
>   tape_put_device() is called from atomic context (under spinlock with
>   IRQs disabled) and from within tape_delayed_next_request() itself,
>   so cancel_delayed_work_sync() there would deadlock or sleep in atomic.
>   tape_generic_remove() runs in process context with no locks held.
>  drivers/s390/char/tape_core.c | 1 +
>  1 file changed, 1 insertion(+)
> 
> diff --git a/drivers/s390/char/tape_core.c b/drivers/s390/char/tape_core.c
> index bd8e3deb11993..cb5db2cabd21a 100644
> --- a/drivers/s390/char/tape_core.c
> +++ b/drivers/s390/char/tape_core.c
> @@ -662,6 +662,7 @@ tape_generic_remove(struct ccw_device *cdev)
>  	if (device) {
>  		sysfs_remove_group(&cdev->dev.kobj, &tape_attr_group);
>  		dev_set_drvdata(&cdev->dev, NULL);
> +		cancel_delayed_work_sync(&device->tape_dnr);
>  		tape_put_device(device);
>  	}
>  }
> -- 
> 2.47.3
> 

      parent reply	other threads:[~2026-10-20 15:44 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-19 22:56 [PATCH v2] s390/tape: cancel delayed work on device removal Tristan Madani
2026-10-19 23:07 ` sashiko-bot
2026-10-20 15:44 ` 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=20261020154424.11179A48-hca@linux.ibm.com \
    --to=hca@linux.ibm.com \
    --cc=agordeev@linux.ibm.com \
    --cc=gor@linux.ibm.com \
    --cc=hoeppner@linux.ibm.com \
    --cc=linux-s390@vger.kernel.org \
    --cc=stable@vger.kernel.org \
    --cc=tristan@talencesecurity.com \
    --cc=tristmd@gmail.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 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.