From: Greg KH <gregkh@suse.de>
To: Christoph Hellwig <hch@lst.de>
Cc: akpm@osdl.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] pci: don't override drv->shutdown unconditionally
Date: Fri, 17 Jun 2005 11:49:14 -0700 [thread overview]
Message-ID: <20050617184914.GA22107@suse.de> (raw)
In-Reply-To: <20050617183057.GA20966@lst.de>
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset=unknown-8bit, Size: 891 bytes --]
On Fri, Jun 17, 2005 at 08:30:57PM +0200, Christoph Hellwig wrote:
> There are many drivers that have been setting the generic driver
> modellevel shutdown callback, and pci thus must not override it.
>
> Without this patch we can have really bad data loss on various
> raid controllers.
Without the kexec patch?
So, why are these drivers setting the shutdown function in the first
place if they don't want it to be called? My change finally enabled
this call, which is what the driver authors expected in the first place.
Without the change I made, the same data loss would be had as drivers
never know that the box is going down.
The fact that a few drivers never tested their shutdown calls is no
reason to penalize the whole kernel.
So, no, I do not want this change in, the drivers should be fixed
properly.
Care to point me to any drivers that need fixing?
thanks,
greg k-h
next prev parent reply other threads:[~2005-06-17 18:50 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-17 18:30 [PATCH] pci: don't override drv->shutdown unconditionally Christoph Hellwig
2005-06-17 18:49 ` Greg KH [this message]
2005-06-17 18:51 ` Christoph Hellwig
2005-06-17 18:53 ` Greg KH
2005-06-17 19:01 ` Greg KH
2005-06-17 19:34 ` Greg KH
-- strict thread matches above, loose matches on Subject: below --
2005-06-17 19:25 [PATCH] PCI: " Greg KH
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=20050617184914.GA22107@suse.de \
--to=gregkh@suse.de \
--cc=akpm@osdl.org \
--cc=hch@lst.de \
--cc=linux-kernel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox