mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@infradead.org>
To: Dave Olien <dmo@osdl.org>
Cc: Christoph Hellwig <hch@infradead.org>,
	marcelo@conectiva.com.br, alan@redhat.com,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] DAC960 open with O_NONBLOCK
Date: Mon, 21 Apr 2003 20:04:30 +0100	[thread overview]
Message-ID: <20030421200430.A11175@infradead.org> (raw)
In-Reply-To: <20030421190111.GA27126@osdl.org>; from dmo@osdl.org on Mon, Apr 21, 2003 at 12:01:11PM -0700

On Mon, Apr 21, 2003 at 12:01:11PM -0700, Dave Olien wrote:
> > What applications?
> 
> John Kamp has run across a libhd applcation from Suse that hit this bug.
> It's some kind of hardware detection application.  It opens devices with
> O_NONBLOCK.  But, it doesn't in fact use the DAC960 pass-through commands.

Do you have source to it?

> The Mylex web page has a RAID management application for DAC960 on Linux that
> is available only in BINARY form.  Unfortunately, it requires
> a Windows front-end to provide a GUI.  So, I haven't actually experimented
> with it. If any application uses the pass-through commands, this would likely
> be it.  But since no one has complained about this being broken, it may
> indicate no one is using this application.

Hmm, breaking it wouldn't be nice, but if they're not willing to
release an updated version we'll just need a LD_PRELOAD wrapper
that maps the open to a new mangment device.

> The pass-through behavior could be made available either through
> a /proc or a sysfs file.

My preference would be a char device (miscdev)

> A related question, why does linux 2.5 continue to have a "struct file *"
> argument to driver release methods? As far as I can tell, that argument
> is always NULL?

->release will change to struct gendisk * at some point.  Touching
it before to just remove the struct file * sounds like a bad idea.


  reply	other threads:[~2003-04-21 18:53 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-04-21 17:24 Dave Olien
2003-04-21 17:37 ` Christoph Hellwig
2003-04-21 19:01   ` Dave Olien
2003-04-21 19:04     ` Christoph Hellwig [this message]
2003-04-21 20:14     ` Alan Cox
2003-04-21 21:35       ` Dave Olien

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=20030421200430.A11175@infradead.org \
    --to=hch@infradead.org \
    --cc=alan@redhat.com \
    --cc=dmo@osdl.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=marcelo@conectiva.com.br \
    /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®