anderson at redhat
Nov 30, 2009, 7:35 AM
Post #2 of 2
(98 views)
Permalink
|
----- "Christoph Hellwig" <hch [at] lst> wrote:
> Hi Dave,
>
> is there a good reason the crash driver is still only stuck in the
> Fedora kernel instead of beeing upstream? We already have the
> restrictive memory device options upstream, so there should be a use
> case for it.
(FWIW, it made it into Fedora long after it was introduced in RHEL...)
Anyway, Bernard Walle's request made far more sense than the crash driver,
and his patch was ultimately rejected:
http://lkml.org/lkml/2008/11/16/117
From: Bernhard Walle <>
Subject: Turn CONFIG_STRICT_DEVMEM in sysctl dev.mem.restricted
Date: Sun, 16 Nov 2008 15:47:45 +0100
So I'm guessing that the crash driver, which is a read-only workaround
for CONFIG_STRICT_DEVMEM kernels, would suffer the same fate.
Dave
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo [at] vger
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
|
