linux-kernel - Re: crash driver in fedora

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [day] [month] [year] [list]

Message-ID: <681767146.799121259595317411.JavaMail.root@zmail05.collab.prod.int.phx2.redhat.com>
Date:	Mon, 30 Nov 2009 10:35:17 -0500 (EST)
From:	Dave Anderson <anderson@...hat.com>
To:	Christoph Hellwig <hch@....de>
Cc:	linux-kernel@...r.kernel.org
Subject: Re: crash driver in fedora


----- "Christoph Hellwig" <hch@....de> 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@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/