| 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
| ||
|
Message-ID: <C1438B59050E1B4C9482FF3266AD6BA32C772D9EB1@gretna.indigovision.com> Date: Tue, 12 Apr 2011 11:30:56 +0100 From: Bruce Stenning <b.stenning@...igovision.com> To: Mark Lord <kernel@...savvy.com> CC: "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>, "linux-ide@...r.kernel.org" <linux-ide@...r.kernel.org> Subject: RE: sata_mv port lockup on hotplug (kernel 2.6.38.2) > > The 2.6.38.2 kernel still exhibits the same lockups that we see with the > > 2.6.26 kernel. > > Okay. Just to help narrow it down a bit, how does 2.6.32 behave ? > > Thanks. Hi Mark, I have reproduced the issue with the 2.6.32 kernel. In case it is of use, the silicon is rev 09 (i.e. C0 stepping) and I am using gcc 4.4.2 to build the kernel and modules. I am currently inserting tracing into 2.6.38.2 to try to work out what is going on. From mv_write_main_irq_mask I can see that the IRQ for each port is still enabled, even when ports stop responding. I see interrupts generated when I hotplug or unplug disks on ports that are not locked up, but no interrupt is generated at all for the ports that are locked (this is from tracing in asm_do_IRQ in arch/arm/kernel/irq.c) One thing I noticed was that there is no spinlock around the mv_save_cached_regs/mv_edma_cfg in mv_hardreset (unlike mv_port_start and mv_port_stop); why is this? Kind Regards, Bruce Stenning, IndigoVision, b <dot> stenning <at> indigovision <dot> com Latest News at: http://www.indigovision.com/index.php/en/news.html
Powered by blists - more mailing lists