All of lore.kernel.org
 help / color / mirror / Atom feed
From: ebiederm@xmission.com (Eric W. Biederman)
To: Anton Blanchard <anton@samba.org>
Cc: Benjamin Herrenschmidt <benh@kernel.crashing.org>,
	james.smart@broadcom.com, dick.kennedy@broadcom.com,
	jejb@linux.vnet.ibm.com, martin.petersen@oracle.com,
	jk@ozlabs.org, linux-scsi@vger.kernel.org
Subject: Re: [PATCH] scsi: lpfc: Add shutdown method for kexec
Date: Mon, 13 Feb 2017 13:21:37 +1300	[thread overview]
Message-ID: <87efz3hre6.fsf@xmission.com> (raw)
In-Reply-To: <20170213104723.7741de0a@kryten> (Anton Blanchard's message of "Mon, 13 Feb 2017 10:47:23 +1100")

Anton Blanchard <anton@samba.org> writes:

> Hi Ben,
>
> On Mon, 13 Feb 2017 10:14:54 +1100
> Benjamin Herrenschmidt <benh@kernel.crashing.org> wrote:
>
>> On Mon, 2017-02-13 at 08:49 +1100, Anton Blanchard wrote:
>> > From: Anton Blanchard <anton@samba.org>
>> > 
>> > We see lpfc devices regularly fail during kexec. Fix this by adding
>> > a shutdown method which mirrors the remove method.  
>> 
>> Or instead finally do what I've been advocating for years (and even
>> sent patches for) which is to have kexec call remove instead of
>> shutdown.

Ben what happened to those patches.  I don't remember them?

>> Shutdown is and has *always* been the wrong thing to do.

I won't argue that.

> Good point, at the very least we should call remove if shutdown doesn't
> exist. Eric: could we make the changes Ben suggests?

Definitely.  That was the original design of the kexec interface
but people were worried about calling remove during reboot might
introduce regressions on the reboot functionality.  So shutdown was
added to be remove without the cleaning up the kernel data structures.

I am all for changing the core to call remove.  That seems to be a more
tested code path (because remove tends to be part of the development
path for modules) and thus much more likely to work in practice.

The challenge with changes in this area is that when the infrastructure
is changed for everyone someone needs to baby sit it until all of the
unexpected issues are resolved.  I was hoping a couple of years ago that
Ben could be that person.

Eric

  reply	other threads:[~2017-02-13  0:26 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-02-12 21:49 [PATCH] scsi: lpfc: Add shutdown method for kexec Anton Blanchard
2017-02-12 23:14 ` Benjamin Herrenschmidt
2017-02-12 23:47   ` Anton Blanchard
2017-02-13  0:21     ` Eric W. Biederman [this message]
2017-02-13  1:01       ` Benjamin Herrenschmidt
2017-02-13 21:57         ` Brian King
2017-02-14  2:04           ` Benjamin Herrenschmidt
2017-02-14 14:56             ` Brian King
2017-02-15  2:44               ` Eric W. Biederman
2017-02-14  2:45           ` Eric W. Biederman
2017-02-14  3:39             ` Benjamin Herrenschmidt
2017-03-06 14:52 ` Mauricio Faria de Oliveira
2017-03-07  3:46   ` Martin K. Petersen
2017-03-07  5:24     ` Benjamin Herrenschmidt
2017-03-07 12:51       ` Mauricio Faria de Oliveira
2017-03-08  1:29         ` Martin K. Petersen

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=87efz3hre6.fsf@xmission.com \
    --to=ebiederm@xmission.com \
    --cc=anton@samba.org \
    --cc=benh@kernel.crashing.org \
    --cc=dick.kennedy@broadcom.com \
    --cc=james.smart@broadcom.com \
    --cc=jejb@linux.vnet.ibm.com \
    --cc=jk@ozlabs.org \
    --cc=linux-scsi@vger.kernel.org \
    --cc=martin.petersen@oracle.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.