linux-kernel - Re: Driver 'sd' needs updating

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Thu, 10 Jan 2008 12:27:22 -0600
From:	James Bottomley <James.Bottomley@...senPartnership.com>
To:	FUJITA Tomonori <fujita.tomonori@....ntt.co.jp>
Cc:	nick@...sn.org, linux-kernel@...r.kernel.org,
	linux-scsi@...r.kernel.org, Greg KH <greg@...ah.com>,
	Kay Sievers <kay.sievers@...y.org>
Subject: Re: Driver 'sd' needs updating


On Thu, 2008-01-10 at 20:38 +0900, FUJITA Tomonori wrote:
> CC'ed linux-scsi and James,
> 
> On Thu, 10 Jan 2008 08:51:50 +0000
> Nick Warne <nick@...sn.org> wrote:
> 
> > 
> > Hi everybody - Happy New Year to you all!
> > 
> > OK, updated to git rc7 yesterday - I now see this in syslog:
> > 
> >    "Driver 'sd' needs updating - please use bus_type methods"
> > 
> > The warning never appeared in RC6, and all google reveals are other
> > peoples logs that are posted about other issues.
> > 
> > Do I need to fix up something here?
> 
> No, you don't. It's harmless, a side effect of:
> 
> commit 751bf4d7865e4ced406be93b04c7436d866d3684
> Author: James Bottomley <James.Bottomley@...senPartnership.com>
> Date:   Wed Jan 2 11:14:30 2008 -0600
> 
>     [SCSI] scsi_sysfs: restore prep_fn when ULD is removed
> 
> 
> It would be better to silence this warning.
> 
> James, we need to reset prep_fn in each ULD? though it's not nice...

Really not nice ... to the extent that we shouldn't do it.  The reset is
in exactly the correct place currently.  If we make it a requirement of
the ULDs its duplication and someone is bound to forget.

It looks like the problem is the warning in
base/driver.c:driver_register() apparently it wants an either/or for
->remove methods (either bus type or driver).  We're actually using the
bus_type methods, but we also have a driver component, sigh.  I suppose
what it's wanting is for me to add a scsi_driver type with remove
methods ... which looks a bit silly since all of the SCSI drivers want
different remove methods.

James


--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/