public inbox for linux-scsi@vger.kernel.org
 help / color / mirror / Atom feed
From: Kay Sievers <kay.sievers@vrfy.org>
To: Jeff Garzik <jeff@garzik.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Linus Torvalds <torvalds@linux-foundation.org>,
	James Bottomley <James.Bottomley@HansenPartnership.com>,
	Andrew Morton <akpm@linux-foundation.org>,
	linux-scsi@vger.kernel.org
Subject: Re: [SCSI] fix media change events for polled devices
Date: Fri, 21 Mar 2008 19:33:46 +0100	[thread overview]
Message-ID: <1206124426.24338.20.camel@lov.site> (raw)
In-Reply-To: <47E3EC67.4050404@garzik.org>

On Fri, 2008-03-21 at 13:12 -0400, Jeff Garzik wrote:
> Linux Kernel Mailing List wrote:
> >     [SCSI] fix media change events for polled devices
> >     
> >     Commit:
> >       a341cd0f (SCSI: add asynchronous event notification API)
> >     breaks:
> >       285e9670 (sr,sd: send media state change modification events)
> >     by introducing an event filter, which is removed here, to make
> >     events, we are depending on, happen again.
> 
> 
> By simply reading the code history, it is trivial to verify that this 
> description is false:
> 
> Commit 285e9670 depends on a341cd0f, so by definition it is 285e9670 -- 
> or rather the incomplete update of your original patch that resulted in 
> 285e9670 -- that is broken.

It worked fine with Kristen's patches, and that's where it is coming
from from.

> Since commit 285e9670 is broken, you fixed the wrong thing.
> 
> Furthermore, you broke a userspace interface that was introduced by 
> a341cd0f, by removing the event filter controlled by userspace.

You mean the read-only sysfs attribute? :)

> Did anyone bother to read any code at all?
> 
> When 285e9670 was updated for the scsi_evt_* interface, it should have 
> initialized the supported_events mask.
> 
> And that is the fix -- initialize supported_events according to sr/sd's 
> needs, and revert this change (4d1566ed2100d074ccc654e5cf2e44cdea3a01d0) 
> as obviously broken.

You mean adding a new flag? As every device will "support" these events.

Thanks,
Kay


  parent reply	other threads:[~2008-03-21 18:34 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <200803211559.m2LFxPi6017869@hera.kernel.org>
2008-03-21 17:12 ` [SCSI] fix media change events for polled devices Jeff Garzik
2008-03-21 17:31   ` Linus Torvalds
2008-03-21 19:38     ` James Bottomley
2008-03-21 20:54       ` Jeff Garzik
2008-03-21 20:39     ` Jeff Garzik
2008-03-21 18:33   ` Kay Sievers [this message]
2008-03-21 20:42     ` Jeff Garzik
2008-03-21 20:57       ` Kay Sievers
2008-03-21 21:04       ` James Bottomley
2008-03-21 21:10         ` Jeff Garzik
2008-03-21 19:44   ` James Bottomley
2008-03-21 20:36     ` Jeff Garzik
2008-03-21 21:01       ` James Bottomley
2008-03-21 21:04         ` Jeff Garzik
2008-03-21 21:09           ` James Bottomley
2008-03-21 21:13             ` Jeff Garzik
2008-03-21 21:49               ` James Bottomley
2008-03-21 22:35                 ` Jeff Garzik
2008-03-21 22:52                   ` James Bottomley
2008-03-25  3:09                     ` Jeff Garzik
2008-03-25  3:18                       ` James Bottomley

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=1206124426.24338.20.camel@lov.site \
    --to=kay.sievers@vrfy.org \
    --cc=James.Bottomley@HansenPartnership.com \
    --cc=akpm@linux-foundation.org \
    --cc=jeff@garzik.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-scsi@vger.kernel.org \
    --cc=torvalds@linux-foundation.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