linux-kernel - Re: [PATCH]PCIe AER: reject aer inject if hardware mask error reporting

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 for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20091217133455.GD11466@youquan-linux.bj.intel.com>
Date:	Thu, 17 Dec 2009 08:34:55 -0500
From:	"Youquan,Song" <youquan.song@...ux.intel.com>
To:	Andrew Patterson <andrew.patterson@...com>
Cc:	"Youquan,Song" <youquan.song@...ux.intel.com>,
	jbarnes@...tuousgeek.org, andi@...stfloor.org,
	ying.huang@...el.com, kent.liu@...el.com, youquan.song@...el.com,
	linux-kernel@...r.kernel.org, linux-pci@...r.kernel.org
Subject: Re: [PATCH]PCIe AER: reject aer inject if hardware mask error reporting

Hi Andrew,

I have udpate and sent the patch according to your comments.
 
> >  	dev = pci_get_bus_and_slot(einj->bus, devfn);
> 
> This does not apply.  Please respin against latest linux-2.6 or pci-2.6.
Yes, it is true that it is udapted at 32 final. Thanks.

> >  
> > +	pci_read_config_dword(dev, pos_cap_err + PCI_ERR_COR_MASK, &mask);
> > +	if (einj->cor_status && !(einj->cor_status & ~mask)) {
> > +		ret = -EINVAL;
> > +		printk(KERN_WARNING "The correctable error is masked by device\n");
> 
> You can inject multiple correctable errors with the aer-inject user-land
> tool, so perhaps this should be re-worded as:
> 
> "The correctable error(s) are masked by the device\n"
Yes. it is update.

> You can also simultaneously inject correctable and uncorrectable errors,
> so I don't particularly like returning errors here.  Perhaps you should
> just print the warning message out and just not inject the masked
> errors.
I do not agree with you at this point. If the hardware is not support
some error reporting, it need direct report this information to user
who use aer_inject userspace tool. He need change the his inject
configuration file, rather than kernel report him successful inject
AER but no any useful information at console or dmesg output. 

Anyway, In my mind, it should not be very important issue to stop this patch
 go to mainline. 

Thanks.

-Youquan

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