From: "Bartlomiej Zolnierkiewicz" <bzolnier@gmail.com>
To: "Dave Jones" <davej@redhat.com>,
"Linux Kernel" <linux-kernel@vger.kernel.org>,
linux-ide@vger.kernel.org
Subject: Re: Fix IDE locking error.
Date: Fri, 17 Feb 2006 09:57:13 +0100 [thread overview]
Message-ID: <58cb370e0602170057x59b23957n3e858d5ac4918326@mail.gmail.com> (raw)
In-Reply-To: <20060216223916.GA8463@redhat.com>
On 2/16/06, Dave Jones <davej@redhat.com> wrote:
> This bit us a few kernels ago, and for some reason never made it's way
> upstream.
Because has never been submitted...
> https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=144743
> Kernel panic - not syncing: drivers/ide/pci/piix.c:231:
> spin_lock(drivers/ide/ide.c:c03cef28) already locked by driver/ide/ide-iops.c/1153.
Could we get a decent description of the problem and of the patch?
Starting with the short description: it is piix locking being fixed not IDE one.
As this is piix only patch your bugzilla #144768 is not duplicate of
#144743. Also some people reported the problem for atiixp.c
under #144743 (attixp.c has similar locking problem to piix.c).
So either they didn't care to reopen the bug or it was fixed by
some other change it the core IDE code.
> From: Alan Cox <alan@redhat.com>
> Signed-off-by: Dave Jones <davej@redhat.com>
>
> --- linux-2.6.12/drivers/ide/pci/piix.c~ 2005-07-11 10:23:24.637181320 +0100
> +++ linux-2.6.12/drivers/ide/pci/piix.c 2005-07-11 10:23:24.637181320 +0100
> @@ -203,6 +203,8 @@
> }
> }
>
> +static spinlock_t tune_lock = SPIN_LOCK_UNLOCKED;
> +
> /**
> * piix_tune_drive - tune a drive attached to a PIIX
> * @drive: drive to tune
> @@ -229,7 +231,12 @@
> { 2, 3 }, };
>
> pio = ide_get_best_pio_mode(drive, pio, 5, NULL);
> - spin_lock_irqsave(&ide_lock, flags);
> +
> + /* Master v slave is synchronized above us but the slave register is
> + shared by the two hwifs so the corner case of two slave timeouts in
> + parallel must be locked */
> +
> + spin_lock_irqsave(&tune_lock, flags);
> pci_read_config_word(dev, master_port, &master_data);
> if (is_slave) {
> master_data = master_data | 0x4000;
> @@ -249,7 +256,7 @@
> pci_write_config_word(dev, master_port, master_data);
> if (is_slave)
> pci_write_config_byte(dev, slave_port, slave_data);
> - spin_unlock_irqrestore(&ide_lock, flags);
> + spin_unlock_irqrestore(&tune_lock, flags);
> }
>
> /**
next prev parent reply other threads:[~2006-02-17 8:57 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-16 22:39 Dave Jones
2006-02-17 8:57 ` Bartlomiej Zolnierkiewicz [this message]
2006-02-17 14:28 ` Alan Cox
2006-02-17 14:53 ` Bartlomiej Zolnierkiewicz
2006-02-17 15:33 ` Alan Cox
2006-02-17 15:43 ` Bartlomiej Zolnierkiewicz
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=58cb370e0602170057x59b23957n3e858d5ac4918326@mail.gmail.com \
--to=bzolnier@gmail.com \
--cc=davej@redhat.com \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.kernel.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
all inboxes | Powered by JetHome®