linux-kernel - Re: [BUGS][PATCH] Fixes to the BFS filesystem driver

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]

Date:	Tue, 13 Nov 2007 11:38:52 -0800
From:	Andrew Morton <akpm@...ux-foundation.org>
To:	Dmitri Vorobiev <dmitri.vorobiev@...il.com>
Cc:	tigran@...azian.fsnet.co.uk, viro@....linux.org.uk,
	Linux-kernel <linux-kernel@...r.kernel.org>
Subject: Re: [BUGS][PATCH] Fixes to the BFS filesystem driver

On Tue, 13 Nov 2007 19:32:32 +0300 Dmitri Vorobiev <dmitri.vorobiev@...il.com> wrote:

> Hi Tigran,
> 
> I found a few bugs in the BFS driver. Detailed description of the bugs as well as the steps to reproduce the errors are given in the kernel bugzilla. Please follow these links for more information:
> 
> http://bugzilla.kernel.org/show_bug.cgi?id=9363
> http://bugzilla.kernel.org/show_bug.cgi?id=9364
> http://bugzilla.kernel.org/show_bug.cgi?id=9365
> http://bugzilla.kernel.org/show_bug.cgi?id=9366
> 
> The patch included in this email fixes the bugs described above. Besides, the patch introduces coding style changes to make the BFS driver conform to the requirements specified for Linux kernel code. Finally, I made a few cosmetic changes such as removal of trivial debug output.
> 
> Also, the patch removes the fields `si_lf_ioff' and `si_lf_sblk' of the in-core superblock structure. These fields are initialized but never actually used.
> 
> If you are wondering why I need BFS, here is the answer: I am using this driver in the context of Linux kernel classes I am teaching in the Moscow State University and in the International Institute of Information Technology in Pune, India.

I was wondering ;)  BFS users aren't common.  Thanks for the fixes.

For future reference: we prefer that an individual patch not do more than
one thing.  So it would have been preferable to present this work as a
sequence of patches.

Probably the high-priority patches (ie: bugfixes) should be the earlier
patches in a case like this.  Because then we can backport the fix into
2.6.23 and maybe 2.6.22 with some confidence.  Also, separating out the
cleanups for the bugfixes makes it easier for people to review and
understand the bugfixes.


Still, that's a minor detail compared to getting a filesystem bug fixed so
I merged your change as-is, thanks

-
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/