All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Martin K. Petersen" <martin.petersen@oracle.com>
To: Hannes Reinecke <hare@suse.de>
Cc: "Martin K. Petersen" <martin.petersen@oracle.com>,
	Christoph Hellwig <hch@lst.de>,
	James Bottomley <james.bottomley@hansenpartnership.com>,
	linux-scsi@vger.kernel.org, Calvin Owens <calvinowens@fb.com>
Subject: Re: [PATCH] ses: Fix racy cleanup of /sys in remove_dev()
Date: Fri, 25 Aug 2017 17:36:25 -0400	[thread overview]
Message-ID: <yq1shgf5nza.fsf@oracle.com> (raw)
In-Reply-To: <1503580432-105307-1-git-send-email-hare@suse.de> (Hannes Reinecke's message of "Thu, 24 Aug 2017 15:13:52 +0200")


Hannes,

> Currently we free the resources backing the enclosure device before we
> call device_unregister(). This is racy: during rmmod of low-level SCSI
> drivers that hook into enclosure, we end up with a small window of
> time during which writing to /sys can OOPS. Example trace with
> mpt3sas:

Applied to 4.14/scsi-queue but dropped link to non-public bugzilla.

-- 
Martin K. Petersen	Oracle Linux Engineering

  reply	other threads:[~2017-08-25 21:36 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-08-24 13:13 [PATCH] ses: Fix racy cleanup of /sys in remove_dev() Hannes Reinecke
2017-08-25 21:36 ` Martin K. Petersen [this message]
  -- strict thread matches above, loose matches on Subject: below --
2016-05-13 20:28 Calvin Owens
2016-05-13 20:28 ` Calvin Owens
2016-06-02 22:50 ` Calvin Owens
2016-06-02 22:50   ` Calvin Owens
2016-06-15 20:24   ` Calvin Owens
2016-06-15 20:24     ` Calvin Owens
2016-07-28  1:04     ` Calvin Owens
2016-07-28  1:04       ` Calvin Owens
2016-07-29  1:23       ` Martin K. Petersen
2016-07-29  1:23         ` Martin K. Petersen
2016-08-12 17:45         ` James Bottomley

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=yq1shgf5nza.fsf@oracle.com \
    --to=martin.petersen@oracle.com \
    --cc=calvinowens@fb.com \
    --cc=hare@suse.de \
    --cc=hch@lst.de \
    --cc=james.bottomley@hansenpartnership.com \
    --cc=linux-scsi@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.