linux-kernel - Re: [Bug #14894] pohmelfs: NULL pointer dereference

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

Date:	Tue, 2 Feb 2010 13:18:09 -0800
From:	Greg KH <greg@...ah.com>
To:	Evgeniy Polyakov <zbr@...emap.net>
Cc:	Jens Axboe <jens.axboe@...cle.com>,
	"Rafael J. Wysocki" <rjw@...k.pl>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	Kernel Testers List <kernel-testers@...r.kernel.org>,
	Alexander Beregalov <a.beregalov@...il.com>
Subject: Re: [Bug #14894] pohmelfs: NULL pointer dereference

On Tue, Feb 02, 2010 at 11:57:43PM +0300, Evgeniy Polyakov wrote:
> Hi.
> 
> Sorry, it took really long to catch all the things around, but it is
> better than never.
> 
> History says that commit which introduced per-bdi writeback broke
> pohmelfs, since it does not have backing store device and did not fill
> appropriate superblock entry, which lead to crash on umoount.
> 
> Jens provided a patch below, which I tested to fix the problem.
> There is a problem though, when all writes happend before umount,
> but did net yet written back to storage, get lost. I can not say whether
> this happens because of per-bdi writeback (it should not I think), but
> that's what happens.
> 
> Albeit being a bug, it will not be fixed :)
> The reason is simple, new backing storage for POHMELFS (a distributed
> hash table called elliptics network) is essentially ready and I start
> working on porting POHMELFS to it, which means all its bugs will be
> fixed there^W^Werased and written from scratch.
> 
> Jens, thanks a lot for you patch, Greg please pull it up.
> If you did not find it or can not extract from the reply, I will resend.

Please resend it with a signed-off-by line so that I can apply it.

thanks,

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/