linux-kernel - Re: [GIT BISECT -next] mem.c: could not login on console of fedora 10

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] [day] [month] [year] [list]

Date:	Mon, 14 Sep 2009 13:49:41 +0200
From:	Kay Sievers <kay.sievers@...y.org>
To:	Jin Dongming <jin.dongming@...css.fujitsu.com>
Cc:	Jiri Kosina <jkosina@...e.cz>, gregkh <gregkh@...e.de>,
	LKLM <linux-kernel@...r.kernel.org>,
	Kenji Kaneshige <kaneshige.kenji@...fujitsu.com>,
	Hidetoshi Seto <seto.hidetoshi@...fujitsu.com>
Subject: Re: [GIT BISECT -next] mem.c: could not login on console of fedora 10

2009/9/14 Jin Dongming <jin.dongming@...css.fujitsu.com>:
> When I build and boot -next on fedora 10, I can not login anymore.
> When I input the user name and password, the system does not output
> any message and requires user to input the user name and password
> again and again.
>
> I find the patch which caused this problem with "GIT BISECT" command.
> And the patch is
>    commit 7c4b7daa1878972ed0137c95f23569124bd6e2b1
>    "mem_class: use minor as index instead of searching the array".
>
> Though I don't know the real reason why user could not login, I
> confirmed the patch I made as following could resolve the problem on
> fedora 10.
>
> Signed-off-by: Jin Dongming <jin.dongming@...css.fujitsu.com>
> ---
>  drivers/char/mem.c |    4 ++--
>  1 files changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/char/mem.c b/drivers/char/mem.c
> index bed3503..0491cdf 100644
> --- a/drivers/char/mem.c
> +++ b/drivers/char/mem.c
> @@ -878,8 +878,8 @@ static const struct memdev {
>        [ 4] = { "port", &port_fops, NULL },
>  #endif
>        [ 5] = { "zero", &zero_fops, &zero_bdi },
> -       [ 6] = { "full", &full_fops, NULL },
> -       [ 7] = { "random", &random_fops, NULL },
> +       [ 7] = { "full", &full_fops, NULL },
> +       [ 8] = { "random", &random_fops, NULL },
>        [ 9] = { "urandom", &urandom_fops, NULL },
>        [11] = { "kmsg", &kmsg_fops, NULL },
>  #ifdef CONFIG_CRASH_DUMP

Yeah, that looks messed up and it seems like the right fix.
Greg, care to merge that into the patch in your tree?

Thanks for the fix and sorry,
Kay
--
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/