From: Andrew Morton <akpm@zip.com.au>
To: Anton Altaparmakov <aia21@cantab.net>
Cc: Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH-2.5.13] NTFS 2.0.6 Bugfix/adapt to 2.5.12 changes
Date: Sat, 04 May 2002 16:56:01 -0700 [thread overview]
Message-ID: <3CD47511.79846141@zip.com.au> (raw)
In-Reply-To: <E1747yJ-0005eY-00@storm.christs.cam.ac.uk>
Anton Altaparmakov wrote:
>
> Hi,
>
> I have just sent the below NTFS update to Linus for inclusion. Andrew
> Morton's changes to 2.5.12 broke NTFS because they added fields to
> struct address_space which ntfs obviously wasn't initializing...
Sorry about that, Chief. ra_pages, presumably. That's one
which *has* to be initialised.
I've added quite a lot of "if you didn't provide one then I'll
do the default" code, but that's an interim step - later, all
the address_spaces need to be populated with the right stuff.
> ...
> + /* Initialize the mftbmp address space mapping. */
> + INIT_RADIX_TREE(&vol->mftbmp_mapping.page_tree, GFP_ATOMIC);
> + rwlock_init(&vol->mftbmp_mapping.page_lock);
> + INIT_LIST_HEAD(&vol->mftbmp_mapping.clean_pages);
> + INIT_LIST_HEAD(&vol->mftbmp_mapping.dirty_pages);
> + INIT_LIST_HEAD(&vol->mftbmp_mapping.locked_pages);
> + INIT_LIST_HEAD(&vol->mftbmp_mapping.io_pages);
> + vol->mftbmp_mapping.nrpages = 0;
> + vol->mftbmp_mapping.a_ops = NULL;
> + vol->mftbmp_mapping.host = NULL;
> + INIT_LIST_HEAD(&vol->mftbmp_mapping.i_mmap);
> + INIT_LIST_HEAD(&vol->mftbmp_mapping.i_mmap_shared);
> + spin_lock_init(&vol->mftbmp_mapping.i_shared_lock);
> + vol->mftbmp_mapping.dirtied_when = 0;
> + vol->mftbmp_mapping.gfp_mask = GFP_HIGHUSER;
That's all generic code. It's initialising core
kernel fields. If should be done in the core kernel.
It would be better to split the address_space initialisation
parts out of inode_init_once(), and export the new function...
-
next prev parent reply other threads:[~2002-05-04 23:54 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-04 22:25 Anton Altaparmakov
2002-05-04 23:56 ` Andrew Morton [this message]
2002-05-05 0:41 ` Anton Altaparmakov
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=3CD47511.79846141@zip.com.au \
--to=akpm@zip.com.au \
--cc=aia21@cantab.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
all inboxes | Powered by JetHome®