linux-kernel - Re: [PATCH] genhd fix or ide workaround -- choose one

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: <20061019122516.GA9040@localhost>
Date:	Thu, 19 Oct 2006 16:25:16 +0400
From:	Anton Vorontsov <cbou@...l.ru>
To:	Alan Cox <alan@...rguk.ukuu.org.uk>
Cc:	kernel-discuss@...dhelds.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] genhd fix or ide workaround -- choose one

On Thu, Oct 19, 2006 at 01:05:52PM +0100, Alan Cox wrote:
> Ar Iau, 2006-10-19 am 02:15 +0400, ysgrifennodd Anton Vorontsov:
> > Hi all,
> > 
> > I've caught deadlock inside IDE layer using IDE-CS: after accessing
> > to IDE disk placed in PCMCIA (CF card really), it will never probe
> > again after pulling it from PCMCIA/CF.
> 
> Works for me, and has done for a long time and I've also had no other
> reports of this in the past couple of years so I'm curious what trips it
> in your case ?

It just happens every time on HP iPaq hx4700. hx4700 have internal CF
slot, which is working via pxa2xx pcmcia driver.

Have you tried it recently or about six months ago? Because at that time
it was working for me too, but some kernel change
(I suppose semaphores->completion conversion) unearthed that bug, but I'm
not sure.

> > The kernel is stuck at
> > drivers/ide/ide.c:ide_unregister():604:
> > 
> >         602                 spin_unlock_irq(&ide_lock);
> >         603                 device_unregister(&drive->gendev);
> >         604                 wait_for_completion(&drive->gendev_rel_comp);
> >         605                 spin_lock_irq(&ide_lock);
> 
> We need to know all the references have gone away, if someone has a disk
> referenced and you pull it out we can't clean up immediately so this is
> the right place to get stuck both on a refcounting bug and if you've got
> something holding a reference for real (eg HAL)

No HAL used. No udev used. Bare kernel + static /dev + shell. CF is not
even mounted once.

Have you read comments inside -fix patch? Imho it's obvious that nobody
putting driverfs_device second time, but got it twice.

Thanks,

-- Anton (irc: bd2)
-
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/