From: Kenji Kaneshige <kaneshige.kenji@jp.fujitsu.com>
To: Alexey Dobriyan <adobriyan@gmail.com>,
Yong Zhang <yong.zhang0@gmail.com>
Cc: tglx@linutronix.de, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] genirq: fix incorrect proc spurious output
Date: Wed, 01 Dec 2010 14:26:25 +0900 [thread overview]
Message-ID: <4CF5DC81.1080600@jp.fujitsu.com> (raw)
In-Reply-To: <20101130100742.GA4856@core2.telecom.by>
Thank you for reviewing, Yong, Alexey.
I'll resend the patch with cc:ing stable.
Regards,
Kenji Kaneshige
(2010/11/30 19:07), Alexey Dobriyan wrote:
> On Tue, Nov 30, 2010 at 05:08:13PM +0800, Yong Zhang wrote:
>> 2010/11/30 Kenji Kaneshige<kaneshige.kenji@jp.fujitsu.com>:
>>> Fix the problem that all the /proc/irq/XX/spurious files shows the IRQ
>>> 0 information.
>>>
>>> Current irq_spurious_proc_open() passes on NULL as the 3rd argument,
>>> which is used as an IRQ number in irq_spurious_proc_show(), to the
>>> single_open(). Because of this, all the /proc/irq/XX/spurious file
>>> shows IRQ 0 information regardless of the IRQ number.
>>>
>>> To fix the problem, irq_spurious_proc_open() must pass on the
>>> appropreate data (IRQ number) to single_open().
>>>
>>> Signed-off-by: Kenji Kaneshige<kaneshige.kenji@jp.fujitsu.com>
>>
>> Looks good.
>>
>> Reviewed-by: Yong Zhang<yong.zhang0@gmail.com>
>>
>> BTW, it's introduced by a1afb6371bb5341057056194d1168753f6d77242
>> So should we Cc'ing stable?
>
> Definitely.
>
>>> static int irq_spurious_proc_open(struct inode *inode, struct file *file)
>>> {
>>> - return single_open(file, irq_spurious_proc_show, NULL);
>>> + return single_open(file, irq_spurious_proc_show, PDE(inode)->data);
>>> }
>
>
next prev parent reply other threads:[~2010-12-01 5:26 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-30 8:36 Kenji Kaneshige
2010-11-30 9:08 ` Yong Zhang
2010-11-30 10:07 ` Alexey Dobriyan
2010-12-01 5:26 ` Kenji Kaneshige [this message]
2010-12-01 7:45 ` [tip:irq/urgent] genirq: Fix " tip-bot for Kenji Kaneshige
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=4CF5DC81.1080600@jp.fujitsu.com \
--to=kaneshige.kenji@jp.fujitsu.com \
--cc=adobriyan@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=tglx@linutronix.de \
--cc=yong.zhang0@gmail.com \
/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
Powered by JetHome