From: Ferenc Wagner <wferi@niif.hu>
To: Phillip Lougher <phillip.lougher@gmail.com>
Cc: linux-fsdevel@vger.kernel.org, linux-mtd@lists.infradead.org,
linux-kernel@vger.kernel.org, linux-embedded@vger.kernel.org
Subject: Re: RFC: direct MTD support for SquashFS
Date: Fri, 19 Mar 2010 02:05:50 +0100 [thread overview]
Message-ID: <87d3z1unm9.fsf@tac.ki.iif.hu> (raw)
In-Reply-To: Ferenc Wagner's message of "Fri\, 19 Mar 2010 00\:13\:46 +0100"
Ferenc Wagner <wferi@niif.hu> writes:
> Phillip Lougher <phillip.lougher@gmail.com> writes:
>
>> On Thu, Mar 18, 2010 at 4:38 PM, Ferenc Wagner <wferi@niif.hu> wrote:
>>
>> +static int fill_bdev_super(struct super_block *sb, void *data, int silent)
>> +{
>> + struct squashfs_sb_info *msblk;
>> + struct squashfs_bdev *bdev;
>> + int err = squashfs_fill_super2(sb, data, silent, &squashfs_bdev_ops);
>> + if (err)
>> + return err;
>> +
>> + bdev = kzalloc(sizeof(*bdev), GFP_KERNEL);
>> + if (!bdev)
>> + return -ENOMEM;
>> +
>> + bdev->devblksize = sb_min_blocksize(sb, BLOCK_SIZE);
>> + bdev->devblksize_log2 = ffz(~bdev->devblksize);
>> +
>> + msblk = sb->s_fs_info;
>> + msblk->backend_data = bdev;
>> + return 0;
>> +}
>>
>> This function looks rather 'back-to-front' to me. I'm assuming that
>> squashfs_fill_super2() will be the current fill superblock function?
>
> Yes, with the extra parameter added.
>
>> This function wants to read data off the filesystem through the
>> backend, and yet the backend (bdev, mblk->backend_data) hasn't been
>> initialised when it's called...
>
> It can't be, because msblk = sb->s_fs_info is allocated by
> squashfs_fill_super(). Now it will be passed the ops, so after
> allocating msblk it can also fill out the ops. After that it can read,
> and squashfs_read_data() will call the init, read and free operations of
> the backend.
And here we indeed have a rather fundamental problem. This isn't
specific to the discussed plugin system at all. Even in the current
code, to set msblk->block_size squashfs_fill_super() calls
squashfs_read_table() to read the superblock, which in turn calls
squashfs_read_data(), which uses msblk->block_size to allocate enough
buffer heads, but msblk->block_size just can't be set at this point.
msblk->bytes_used is preset with a dummy value to make the read
possible, but msblk->block_size is not. Fortunately, one buffer head is
allocated each time nevertheless. I wonder what a correct solution
would look lke..
--
Regards,
Feri.
next prev parent reply other threads:[~2010-03-19 1:06 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-16 13:38 RFC: direct MTD support for SquashFS Ferenc Wagner
2010-03-16 14:26 ` Peter Korsgaard
2010-03-16 19:18 ` Vitaly Wool
2010-03-18 16:38 ` Ferenc Wagner
2010-03-18 21:40 ` Phillip Lougher
2010-03-18 22:52 ` Ferenc Wagner
2010-03-19 1:05 ` Ferenc Wagner [this message]
2010-03-19 7:30 ` Phillip Lougher
2010-03-19 14:12 ` Ferenc Wagner
2010-03-23 11:34 ` Ferenc Wagner
2010-03-23 20:45 ` Ferenc Wagner
2010-03-23 20:47 ` Ferenc Wagner
2010-03-24 5:23 ` Phillip Lougher
2010-03-24 6:35 ` Peter Korsgaard
2010-03-24 11:28 ` Ferenc Wagner
2010-03-24 11:35 ` Peter Korsgaard
2010-03-24 13:48 ` Ferenc Wagner
[not found] ` <1269955969-26123-3-git-send-email-wferi@niif.hu>
2010-03-30 16:50 ` [PATCH 2/3] squashfs: gather everything block device specific into block.c Ferenc Wagner
[not found] ` <1269955969-26123-1-git-send-email-wferi@niif.hu>
2010-03-31 6:35 ` [PATCH 0/3] RFC: direct MTD support for SquashFS Marco Stornelli
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=87d3z1unm9.fsf@tac.ki.iif.hu \
--to=wferi@niif.hu \
--cc=linux-embedded@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=phillip.lougher@gmail.com \
/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