From: Jan Kara <jack@suse.cz>
To: Ralf Hornik Mailings <ralf@best.homeunix.org>
Cc: linux-fsdevel@vger.kernel.org
Subject: Re: block_device_operations change since 2.6.27.X
Date: Mon, 10 May 2010 23:06:38 +0200 [thread overview]
Message-ID: <20100510210637.GA23924@quack.suse.cz> (raw)
In-Reply-To: <20100506150000.78121ikdk2550768@www.ralf-hornik.de>
On Thu 06-05-10 15:00:00, Ralf Hornik Mailings wrote:
> Ralf Hornik Mailings <ralf@best.homeunix.org> wrote:
>
> >I'm trying to port adics cvfs module to any newer kernel and had
> >to figure out that the prototype of "block_device_operations" has
> >become incompatible with code formerly used against kernel <=
> >2.6.27.46
> >
> >Unfortunately the documentation in filesystems/Locking does still
> >point to the old prototype.
> >Can somebody give me some hints how to use the new
> >block_device_operations defined in blkdev.h or send me some new
> >dokumentation?
>
> Can noone tell me how to use the new object?
It's a bit hard to tell without knowing more details about the problem
you have. I guess your problem is that originally the functions were passed
struct inode * and struct file * while now they are passed struct
block_device and fmode_t. That should be fairly easy to solve as most
drivers use just inode->i_bdev (now passed directly) and file->f_flags
(also passed directly in the new convention). You can have a look e.g. at
commit 0338e29178795f0df0e1f3705b5d3effe9c95ff7 where drivers/scsi/sd.c is
converted.
Honza
--
Jan Kara <jack@suse.cz>
SUSE Labs, CR
next prev parent reply other threads:[~2010-05-10 21:06 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-04 13:00 block_device_operations change since 2.6.27.X Ralf Hornik Mailings
2010-05-06 13:00 ` Ralf Hornik Mailings
2010-05-10 21:06 ` Jan Kara [this message]
[not found] ` <20100507092623.40735f4vurpadme7@www.ralf-hornik.de>
2010-05-15 6:20 ` FWD: " Al Viro
2010-05-17 8:14 ` Ralf Hornik Mailings
-- strict thread matches above, loose matches on Subject: below --
2010-05-04 12:41 Ralf Hornik Mailings
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=20100510210637.GA23924@quack.suse.cz \
--to=jack@suse.cz \
--cc=linux-fsdevel@vger.kernel.org \
--cc=ralf@best.homeunix.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;
as well as URLs for NNTP newsgroup(s).