linux-kernel - Re: [PATCH] scsi: remove CDROM not ready printk

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]

Message-Id: <1212074573.3428.32.camel@localhost.localdomain>
Date:	Thu, 29 May 2008 10:22:53 -0500
From:	James Bottomley <James.Bottomley@...senPartnership.com>
To:	Gerb Stralko <gerb.stralko@...il.com>
Cc:	Andrew Morton <akpm@...ux-foundation.org>,
	linux-kernel@...r.kernel.org, linux-scsi@...r.kernel.org
Subject: Re: [PATCH] scsi: remove CDROM not ready printk

On Thu, 2008-05-29 at 11:04 -0400, Gerb Stralko wrote:
> On Thu, May 29, 2008 at 10:55 AM, James Bottomley
> <James.Bottomley@...senpartnership.com> wrote:
> > On Thu, 2008-05-29 at 10:35 -0400, Gerb Stralko wrote:
> >> So is that printk really needed?  Should the kernel even need to print
> >> a message like that, esp. if user-space is handling state updates and
> >> notifications.  Or do i need to configure hald to be quietier?   FWIW
> >> I'm using fedora core 9 and hald version:
> >> -bash-3.2$ /usr/sbin/hald --version
> >> HAL package version: 0.5.11
> >
> > Actually, I misspoke; it's set internally via sets of ioctls.  However,
> > it's designed only to show on ioctls that do medium requiring things.
> >
> > I'm also using FC9 and I see no such messages (and for noisy cgc,
> > they're printed out for every action on the CD).  You have some
> > application that's poking the CD wrongly (probably not hal), so you
> > really need to find out what it is.  It may be pointing to some other
> > error in the kernel that needs fixing, but simply removing the message
> > is covering up the issue.
> >
> > To help track the application, you could update the printk to print out
> > current->comm and current->pid.  That would tell you who is responsible
> >
> > James
> >
> >
> >
> Okay, i'll do some investigation and see if I can track this down,
> I'll let you know.   Thanks for the info.
> 
> Are you using GNOME or KDE?  I'm currently using KDE.

I'm using gnome ... there are intermittent reports of kde problems
mainly with k3b though (the burner program), but if you put the printk
in it should identify the application.

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/