public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@linux-foundation.org>
To: Dmitri Vorobiev <dmitri.vorobiev@gmail.com>
Cc: tigran@aivazian.fsnet.co.uk, viro@ftp.linux.org.uk,
	Linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [BUGS][PATCH] Fixes to the BFS filesystem driver
Date: Tue, 13 Nov 2007 11:38:52 -0800	[thread overview]
Message-ID: <20071113113852.386219f6.akpm@linux-foundation.org> (raw)
In-Reply-To: <4739D1A0.20805@gmail.com>

On Tue, 13 Nov 2007 19:32:32 +0300 Dmitri Vorobiev <dmitri.vorobiev@gmail.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


      reply	other threads:[~2007-11-13 19:44 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-11-13 16:32 [BUGS][PATCH] Fixes to the BFS filesystem driver Dmitri Vorobiev
2007-11-13 19:38 ` Andrew Morton [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20071113113852.386219f6.akpm@linux-foundation.org \
    --to=akpm@linux-foundation.org \
    --cc=dmitri.vorobiev@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=tigran@aivazian.fsnet.co.uk \
    --cc=viro@ftp.linux.org.uk \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox