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: <4F8389A0.6020205@intel.com>
Date:	Tue, 10 Apr 2012 09:15:12 +0800
From:	Alex Shi <alex.shi@...el.com>
To:	Alex Shi <lkml.alex@...il.com>
CC:	JBottomley@...allels.com, Nagalakshmi.Nandigama@....com,
	linux-scsi@...r.kernel.org, linux-kernel@...r.kernel.org,
	roland@...estorage.com
Subject: Re: [PATCH] scsi/mpt2sas: fix unsafe preempt setting for ioc

On 04/06/2012 07:54 PM, Alex Shi wrote:

> Without the following patch, the driver will have many complain after
> smp_processor_id debug enabled.
> 
> So would you like consider to pick this patch or find a better way to
> remove them?


Anyone like to have a look on the following complain?

> 
> Call Trace:^M
>  [<ffffffff81325f77>] debug_smp_processor_id+0xe7/0x100^M
>  [<ffffffffa0016324>] mpt2sas_base_put_smid_default+0x34/0x70 [mpt2sas]^M
>  [<ffffffffa0016472>] _base_event_notification+0x112/0x240 [mpt2sas]^M
>  [<ffffffffa0016a11>] _base_make_ioc_operational+0x471/0x1240 [mpt2sas]^M
>  [<ffffffff810b9963>] ? lockdep_init_map+0xa3/0x560^M
>  [<ffffffff810be4fd>] ? trace_hardirqs_on_caller+0x10d/0x1a0^M
>  [<ffffffff810b8588>] ? debug_mutex_init+0x38/0x50^M
>  [<ffffffffa00193c7>] mpt2sas_base_attach+0x1237/0x1630 [mpt2sas]^M
>  [<ffffffffa001ecf8>] _scsih_probe+0x408/0x620 [mpt2sas]^M
>  [<ffffffff8133c64c>] local_pci_probe+0x5c/0xd0^M
>  [<ffffffff8133df41>] pci_device_probe+0x101/0x120^M
>  [<ffffffff814190dc>] driver_probe_device+0x9c/0x300^M
>  [<ffffffff814193eb>] __driver_attach+0xab/0xb0^M
>  [<ffffffff81419340>] ? driver_probe_device+0x300/0x300^M
>  [<ffffffff8141747e>] bus_for_each_dev+0x5e/0x90^M
>  [<ffffffff81418cee>] driver_attach+0x1e/0x20^M
>  [<ffffffff814188e0>] bus_add_driver+0x1c0/0x2b0^M
> 


--
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/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ