linux-kernel - Re: 2.6.23-rc6-mm1

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:	Wed, 19 Sep 2007 16:44:48 -0700
From:	David Brownell <david-b@...bell.net>
To:	Chuck Ebbert <cebbert@...hat.com>, tilman@...p.cc,
	akpm@...ux-foundation.org
Cc:	linux-kernel@...r.kernel.org, gregkh@...e.de, a.zummo@...ertech.it
Subject: Re: 2.6.23-rc6-mm1

> From: Andrew Morton <akpm@...ux-foundation.org>

> > <4>[   21.211942] Duplicate file names "rtc" detected
>
> Nah, that's an rtc-specific problem.

RTC-related ... but it's a procfs bug, since it's procfs which doesn't
even bother to check for duplicate names before it registers files.
And it's that duplication which is the problem.  Try the patch in
this message

  http://lkml.org/lkml/2007/9/19/18

> I think David says that it's actually not a problem, but I didn't
> really understand how this can be?

I said it's not an RTC problem ... it's a procfs problem.

Trying to fix procfs bugs by changing RTC code is futile.  ;)

> From: Chuck Ebbert <cebbert@...hat.com>
>
> AFAICT the rtc problem is caused by misconfiguration: both the new
> and old rtc driver have been built and they are both trying to load.

That _shouldn't_ be a problem at all; only one of them should be
able to bind to that hardware.

The only problem I see in these messages is that procfs bug.

- Dave

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