From: Boaz Harrosh <bharrosh@panasas.com>
To: Al Viro <viro@ZenIV.linux.org.uk>
Cc: Randy Dunlap <randy.dunlap@oracle.com>, linux-scsi@vger.kernel.org
Subject: Re: [PATCH -next] osd_uld: fix printk format warning
Date: Thu, 30 Apr 2009 13:30:07 +0300 [thread overview]
Message-ID: <49F97DAF.2050605@panasas.com> (raw)
In-Reply-To: <20090429185128.GN8633@ZenIV.linux.org.uk>
On 04/29/2009 09:51 PM, Al Viro wrote:
> On Wed, Apr 29, 2009 at 09:26:31AM -0700, Randy Dunlap wrote:
>> From: Randy Dunlap <randy.dunlap@oracle.com>
>>
>> Fix printk format warnings in osd_uld:
>>
>> drivers/scsi/osd/osd_uld.c:191: warning:format '%s' expects type 'char *', but argument 2 has type 'struct path'
>>
>> Also fix a small typo.
>
> Applied, will fold on reorder. Thanks for catching that one and apologies
> for missing the original posting (I am subscribed to linux-scsi, but...)
>
> Incidentally, what the hell is going with ->i_cdev in there? Boaz?
Thanks for asking. The thing is that this function is called from within
the kernel by exofs. Now I have found that if user-mode as never opened
an handle on my char-device, then inode->i_cdev is NULL even though it is
registered and found. My mount utility for exofs does an open/close on the
char-device before calling the Kernel mounter, but this is just a script
and can be missed by users. (I guess I need to submit an mount.exofs. where
should it be submitted?)
Alternatively we perhaps need a udev rule that, one - loads osd.ko when
OSD_TYPE devices are discovered by scsi (like sd), and two - do the above
open/close. I was meaning to ask someone about these things.
Much obliged
Boaz
next prev parent reply other threads:[~2009-04-30 10:30 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20090429092631.a76e79c5.randy.dunlap@oracle.com>
2009-04-29 18:51 ` [PATCH -next] osd_uld: fix printk format warning Al Viro
2009-04-30 10:30 ` Boaz Harrosh [this message]
2009-05-03 18:35 ` Al Viro
2009-05-03 19:02 ` Al Viro
2009-05-04 16:09 ` Boaz Harrosh
2009-05-04 18:30 ` Al Viro
2009-04-23 21:57 Randy Dunlap
2009-04-26 15:32 ` Boaz Harrosh
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=49F97DAF.2050605@panasas.com \
--to=bharrosh@panasas.com \
--cc=linux-scsi@vger.kernel.org \
--cc=randy.dunlap@oracle.com \
--cc=viro@ZenIV.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