linux-kernel - Re: Fwd: [PATCH v7 1/2] x86: Add Isolated Memory Regions for Quark X1000

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]

Date:	Fri, 30 Jan 2015 12:57:29 +0000
From:	Bryan O'Donoghue <pure.logic@...us-software.ie>
To:	Andy Shevchenko <andy.shevchenko@...il.com>,
	Thomas Gleixner <tglx@...utronix.de>,
	Ingo Molnar <mingo@...hat.com>,
	"H. Peter Anvin" <hpa@...or.com>,
	"x86@...nel.org" <x86@...nel.org>,
	"dvhart@...radead.org" <dvhart@...radead.org>,
	"Ong, Boon Leong" <boon.leong.ong@...el.com>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: Fwd: [PATCH v7 1/2] x86: Add Isolated Memory Regions for Quark
 X1000

On 30/01/15 12:55, Bryan O'Donoghue wrote:
> Oops.
>
> Hit reply not reply-all

On 30/01/15 12:03, Andy Shevchenko wrote:
 >> +               return -ENOMEM;
 >
 > When CONFIG_DEBUGFS=n, you will get error pointer here, which is not 
NULL.
 >
 > So, the proper check is
 > if (IS_ERR())
 >   return PTR_ERR();
 > if (!file)
 >   return -ENOMEM;

Yeah I saw that. Also saw that most other code doesn't bother trapping
those return values - so skipped it.
No issue adding.

 >
 >> +               } else {
 >> +                       reg = i;
 >
 > Do we go always through all IMRs and choose the last one?
 > If no, break is missed here.

Yep - we always choose the last one.


 >> +               }
 >> +       }
 >> +
 >> +       /* Error out if we have no free IMR entries. */
 >> +       if (reg == -1) {
 >> +               ret = -ENODEV;
 >
 > -ENOMEM ? Like you said there is no *free* IMR.

OK

 >> + * imr_remove_range(0, size, base); delete IMR at index 0 base/size 
ignored.
 >> + * imr_remove_range(-1, base, size); delete IMR from base to base+size.
 >
 > (size, base) or (base, size) ?

base, size that's a documentation typo :)

 >> +
 >> +       ret = imr_check_params(base, size);
 >> +       if (ret == -EINVAL || (ret == -ENOMEM && reg == -1))
 >
 > reg base size (0 correct, 1 wrong):
 >
 > 0 0 0 â€” which should be used? what is the priority?
 > 0 x 1 â€” index
 > 0 1 x â€” index
 > 1 0 0 â€” address
 > 1 0 1 â€” an error
 > 1 1 1 â€” an error
 >
 > Thus, could it be simpler? Like
 > if (reg < 0 && ret) ?

ret will be EINVAL for unaligned base or size
ret will be ENOMEM when reg == -1 and size == 0

I could probably write it like this to make it clearer
(ret == -EINVAL || (reg == -1 && size == 0)
	return -EINVAL;

traps unaligned input - for address range tear-down
traps zero sized - for address range tear-down

Allows index based teardown i.e. reg >= 0

 > if (ret)
 >
 >> +               pr_warn("debugfs register failed!\n");
 >
 > Do we actually need this? Or move it to debug level.

It was your suggestion @ a previous review ....

 > Here is the mix of kernel levels. What about to align them?
 >
 > For example I doubt we need to distinguish messages by level:
 >
 > pr_info();
 > vprintk(KERN_INFO fmt, â€¦);

OK fine.

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