linux-kernel - Re: [PATCH -v2 3/7] x86, NMI, Rename memory parity error to PCI SERR error

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: <20100927153315.GB26290@redhat.com>
Date:	Mon, 27 Sep 2010 11:33:15 -0400
From:	Don Zickus <dzickus@...hat.com>
To:	Robert Richter <robert.richter@....com>
Cc:	Huang Ying <ying.huang@...el.com>, Ingo Molnar <mingo@...e.hu>,
	"H. Peter Anvin" <hpa@...or.com>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	Andi Kleen <andi@...stfloor.org>
Subject: Re: [PATCH -v2 3/7] x86, NMI, Rename memory parity error to PCI SERR
 error

On Mon, Sep 27, 2010 at 11:00:56AM +0200, Robert Richter wrote:
> On 27.09.10 04:39:20, Huang Ying wrote:
> > > I already commented on this, patch #1 and #3 are basically the same in
> > > most parts which should be merged. What remains then in this patch is
> > > the modified printk() and the comment. Both could be added to #1 too
> > > which is then some sort of code cleanup patch.
> > 
> > Don thinks it is Ok to keep 2 patches.
> 
> I don't like reviewing new changes which are thrown away with the next
> patch. I review things twice and it is much harder to see what really
> changed then. Also we should have a clean history.

I didn't care either way.  But if it makes it easier to review, it's nice
to keep reviewers happy too. :-)

Hunag, I think there is going to be a V3 of this series, could you just
combine these patches then?

> 
> And with git it is fairly easy to join patches.
> 
> > 
> > > >  #define NMI_REASON_CLEAR_IOCHK	0x08
> > > >  #define NMI_REASON_CLEAR_MASK	0x0f
> > > >  
> > > > --- a/arch/x86/kernel/traps.c
> > > > +++ b/arch/x86/kernel/traps.c
> > > > @@ -301,15 +301,14 @@ gp_in_kernel:
> > > >  }
> > > >  
> > > >  static notrace __kprobes void
> > > > -mem_parity_error(unsigned char reason, struct pt_regs *regs)
> > > > +pci_serr_error(unsigned char reason, struct pt_regs *regs)
> > > >  {
> > > > -	printk(KERN_EMERG
> > > > -		"Uhhuh. NMI received for unknown reason %02x on CPU %d.\n",
> > > > -			reason, smp_processor_id());
> > > > -
> > > > -	printk(KERN_EMERG
> > > > -		"You have some hardware problem, likely on the PCI bus.\n");
> > > > +	printk(KERN_EMERG "NMI: PCI system error (SERR).\n");
> > > 
> > > You should keep reporting the cpu id to identify the affected node and
> > > also the reason.
> > 
> > Ok. I will add CPU ID in message. Because we know the reason, I don't
> > think we need the reason in message.
> 
> You only know that bit 7 is set, not the rest. As this is an error
> message we should provide as much information as possible.

Well, what other info do we know besides that bit being set?  (I wish we
had more, but I don't think we do)

Cheers,
Don
--
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/