linux-kernel - Re: crash failure with 2.6.36-rc3 vmcore

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>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <20100905062255.GA18184@suse.de>
Date:	Sat, 4 Sep 2010 23:22:55 -0700
From:	Greg KH <gregkh@...e.de>
To:	Guenter Roeck <guenter.roeck@...csson.com>
Cc:	CAI Qian <caiqian@...hat.com>, Dave Anderson <anderson@...hat.com>,
	"tj@...nel.org" <tj@...nel.org>,
	linux-kernel <linux-kernel@...r.kernel.org>
Subject: Re: crash failure with 2.6.36-rc3 vmcore

On Sat, Sep 04, 2010 at 10:06:25PM -0700, Guenter Roeck wrote:
> I browsed through the code a bit. Looks like the module owner will need to make
> the necessary changes. The code now seems to depend on kernel internal structure
> elements. Not sure if that is a good idea in the first place. At least for
> the attribute owner it will have to be changed to not depend on its existence.
> 
> Of course, one could also argue that the field should be re-introduced in 
> the kernel to make the utility work w/o changes. However, I don't think it
> would be a good idea to hold the kernel hostage for such problems.

You're kidding, right?  You should have tools flexable to handle the
fact that the internal kernel structures change all the time like this.
If not, your tools are broken.

good luck,

greg k-h
--
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/