linux-kernel - Re: [PATCH 12/41] mxser: allow overlapping vector

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:	Mon, 13 Aug 2012 11:20:55 +0930
From:	Rusty Russell <rusty@...abs.org>
To:	Jiri Slaby <jslaby@...e.cz>, gregkh@...uxfoundation.org
Cc:	alan@...ux.intel.com, linux-kernel@...r.kernel.org,
	jirislaby@...il.com
Subject: Re: [PATCH 12/41] mxser: allow overlapping vector

On Tue,  7 Aug 2012 21:47:37 +0200, Jiri Slaby <jslaby@...e.cz> wrote:
> For many cards, this saves some IO space because interrupt status port
> has precedence over the rest of ports on the card. Hence it can be
> mapped to a hole in I/O ports.
> 
> Here we add a kernel parameter which allows that if a user wants to.
> But they need to explicitly enable it by a module parameter.
> 
> Signed-off-by: Jiri Slaby <jslaby@...e.cz>
> ---
>  drivers/tty/mxser.c |   35 +++++++++++++++++++++++++++++++----
>  1 file changed, 31 insertions(+), 4 deletions(-)
> 
> diff --git a/drivers/tty/mxser.c b/drivers/tty/mxser.c
> index c162ee9..e64fe40 100644
> --- a/drivers/tty/mxser.c
> +++ b/drivers/tty/mxser.c
> @@ -2337,11 +2337,36 @@ static struct tty_port_operations mxser_port_ops = {
>   * The MOXA Smartio/Industio serial driver boot-time initialization code!
>   */
>  
> +static bool allow_overlapping_vector;
> +module_param(allow_overlapping_vector, bool, 444);

You mean 0444, right?

Cheers,
Rusty.
--
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/