public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Adrian Bunk <bunk@stusta.de>
To: col-pepper@catking.net
Cc: linux-kernel@vger.kernel.org
Subject: Re: [RFC/PATCH] - revert generic_fillattr stat->blksize to PAGE_CACHE_SIZE
Date: Sun, 3 Dec 2006 14:48:21 +0100	[thread overview]
Message-ID: <20061203134821.GB3442@stusta.de> (raw)
In-Reply-To: <op.tjzjdji6q8etvz@linbox.localdomain>

On Sun, Dec 03, 2006 at 02:21:09PM +0100, col-pepper@catking.net wrote:

> I am using a 2.6.18.2 based kernel and see lots of broken fs due to this  
> "diet". eg cloop
> 
> I hope some general lessons can be drawn about the necessity and  
> desirablility of such changes that (predictably) invoke broadband breakage.

Lessons 1-99:
Get your modules included in the kernel.

> This kind of change and the breakage and dependancy issues they create are  
> what makes linux a nightmare to maintain.
>...

s/linux/external modules not submitted for inclusion in the kernel/

> What kernel release contains code where all this calms down and I dont  
> need to search patches and updates for modules in order to get basics to  
> work again?
>...

None, the Linux development model is based on the fact that such changes 
are considered perfectly OK as long as all in-kernel users are being 
fixed.

The solution for your problem is that the authors of the modules you 
are using should get their modules included in the Linux kernel - and 
they'll be automatically fixed when someone changes an in-kernel API.

> Thanks for your replys.

cu
Adrian

-- 

       "Is there not promise of rain?" Ling Tan asked suddenly out
        of the darkness. There had been need of rain for many days.
       "Only a promise," Lao Er said.
                                       Pearl S. Buck - Dragon Seed


  reply	other threads:[~2006-12-03 13:48 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-12-03 13:21 [RFC/PATCH] - revert generic_fillattr stat->blksize to PAGE_CACHE_SIZE col-pepper
2006-12-03 13:48 ` Adrian Bunk [this message]
  -- strict thread matches above, loose matches on Subject: below --
2006-11-06 21:50 Eric Sandeen
2006-11-06 22:27 ` Dave Kleikamp
2006-11-06 22:37   ` Eric Sandeen
2006-11-07  0:26   ` Steve French
2006-11-07 13:40     ` Dave Kleikamp
2006-11-07 15:34       ` Dave Kleikamp
2006-11-07 15:50         ` Steve French
2006-11-06 23:05 ` Christoph Hellwig
2006-11-06 23:15   ` Eric Sandeen
2006-11-06 23:17     ` Christoph Hellwig
2006-11-06 23:28       ` Eric Sandeen
2006-11-07  0:08     ` Andreas Dilger
2006-11-07  0:13       ` Hua Zhong
2006-11-07  1:39       ` Eric Sandeen
2006-11-07  3:43     ` Theodore Tso
2006-11-07  4:02       ` Eric Sandeen

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=20061203134821.GB3442@stusta.de \
    --to=bunk@stusta.de \
    --cc=col-pepper@catking.net \
    --cc=linux-kernel@vger.kernel.org \
    /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