From: Aravind Gopalakrishnan <aravind.gopalakrishnan@amd.com>
To: Borislav Petkov <bp@alien8.de>
Cc: <dougthompson@xmission.com>, <mchehab@osg.samsung.com>,
<linux-edac@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 3/6] edac, mce_amd_inj: Modify flags attrigute to use string arguments
Date: Mon, 1 Jun 2015 14:16:47 -0500 [thread overview]
Message-ID: <556CAF9F.6080008@amd.com> (raw)
In-Reply-To: <20150529134943.GF31435@pd.tnic>
On 5/29/2015 8:49 AM, Borislav Petkov wrote:
> On Wed, May 27, 2015 at 02:03:35PM -0500, Aravind Gopalakrishnan wrote:
>>
>> +#define MAX_FLAG_OPT_SIZE 10
> Why 10?
>
> This should be 2 and increased when another, longer injection type
> string gets introduced.
>
So I hit an issue when I have this as 2 and moving 'ret = cnt' statement
(in flags_write() below) to after the check for MAX_FLAG_OPT_SIZE.
The problem was, if I did echo hw > flags;
I would get an error on dmesg like so-
[ 78.692949] flags_write: Invalid flags value:
But the write would have actually gone through. i.e, if we do cat flags,
the output was 'hw'.
The issue seems to be that 'cnt' of flags_write() is 3 (after accounting
for a terminating NULL) when we enter the function (for this case),
Since we move 'ret = cnt;' statement to after the check, we end up
returning 2.
And since it is less than 'cnt', we re-enter flags_write() for the final
NULL character.
At this point, our comparisons with flags_options[] fail and we end up
returning -EINVAL from __set_inj().
Hence the error on dmesg..
The fix to this was simply having MAX_FLAG_OPT_SIZE as 3. In this case,
we already account for the NULL and flags_write()
returns the correct value upon success.
So I shall go ahead and make that change to MAX_FLAG_OPT_SIZE as 3 and
increase it in subsequent patch for the apic interrupts.
Thanks,
-Aravind.
>>
>> -DEFINE_SIMPLE_ATTRIBUTE(flags_fops, flags_get, flags_set, "%llu\n");
>> +static ssize_t flags_write(struct file *filp, const char __user *ubuf,
>> + size_t cnt, loff_t *ppos)
>> +{
>> + char buf[MAX_FLAG_OPT_SIZE + 1];
>> + int err;
>> + size_t ret;
>> +
>> + ret = cnt;
> You're assigning cnt to ret here...
>
>> +
>> + if (cnt > MAX_FLAG_OPT_SIZE)
>> + cnt = MAX_FLAG_OPT_SIZE;
> ... but correcting cnt afterwards. The assignment should be *after* that
> correction.
>
>> +
>> + if (copy_from_user(&buf, ubuf, cnt))
>> + return -EFAULT;
>> +
>> + buf[cnt] = 0;
>> +
>> + /* strip whitespaces.. */
>> + strstrip(buf);
>> +
>> + err = __set_inj(buf, cnt - 1);
>> + if (err) {
>> + pr_err("%s: Invalid flags value: %s\n", __func__, buf);
>> + return err;
>> + }
>> +
>> + *ppos += ret;
>> +
>> + return ret;
>> +}
>> +
>>
next prev parent reply other threads:[~2015-06-01 19:17 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-27 19:03 [PATCH 0/6] Updates to EDAC mce_amd_inj Aravind Gopalakrishnan
2015-05-27 19:03 ` [PATCH 1/6] edac, mce_amd_inj: Use MCE_INJECT_GET for bank Aravind Gopalakrishnan
2015-05-27 19:03 ` [PATCH 2/6] edac, mce_amd_inj: Rework sanity check for inj_bank_set Aravind Gopalakrishnan
2015-05-27 19:03 ` [PATCH 3/6] edac, mce_amd_inj: Modify flags attrigute to use string arguments Aravind Gopalakrishnan
2015-05-29 13:49 ` Borislav Petkov
2015-05-29 18:20 ` Aravind Gopalakrishnan
2015-05-29 19:05 ` Borislav Petkov
2015-05-29 19:12 ` Aravind Gopalakrishnan
2015-06-01 19:16 ` Aravind Gopalakrishnan [this message]
2015-05-27 19:03 ` [PATCH 4/6] edac, mce_amd_inj: Add capability to trigger apic interrupts Aravind Gopalakrishnan
2015-05-29 15:36 ` Borislav Petkov
2015-05-29 18:27 ` Aravind Gopalakrishnan
2015-05-29 19:18 ` Borislav Petkov
2015-05-27 19:03 ` [PATCH 5/6] edac, mce_amd_inj: Add README file Aravind Gopalakrishnan
2015-05-29 15:38 ` Borislav Petkov
2015-05-29 18:29 ` Aravind Gopalakrishnan
2015-05-27 19:03 ` [PATCH 6/6] edac, mce_amd_inj: Inject errors on NBC for bank 4 errors Aravind Gopalakrishnan
2015-05-29 16:00 ` Borislav Petkov
2015-05-29 18:52 ` Aravind Gopalakrishnan
2015-05-29 19:23 ` Borislav Petkov
2015-05-29 19:27 ` Aravind Gopalakrishnan
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=556CAF9F.6080008@amd.com \
--to=aravind.gopalakrishnan@amd.com \
--cc=bp@alien8.de \
--cc=dougthompson@xmission.com \
--cc=linux-edac@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mchehab@osg.samsung.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