linux-kernel - Re: kernel oops after ACPI dock initialization fails

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 for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-Id: <20070508152904.c52d258c.kristen.c.accardi@intel.com>
Date:	Tue, 8 May 2007 15:29:04 -0700
From:	Kristen Carlson Accardi <kristen.c.accardi@...el.com>
To:	Chuck Ebbert <cebbert@...hat.com>
Cc:	linux-kernel <linux-kernel@...r.kernel.org>
Subject: Re: kernel oops after ACPI dock initialization fails

On Tue, 08 May 2007 17:54:40 -0400
Chuck Ebbert <cebbert@...hat.com> wrote:

> Chuck Ebbert wrote:
> > In 2.6.21.1 when dock driver initialization fails it does a kfree()
> > of dock_station. (Below, this is due to some error installing a
> > notify handler.) Later when a bay is discovered it calls 
> > is_dock_device() which attempts to lock the (nonexistent)
> > dock_station. Reason is this test in is_dock_device():
> > 
> >         if (!dock_station)
> >                 return 0;
> > 
> > dock_station is 0x6b6b6b6b after being freed. Either it needs
> > to be zeroed or some other flag should be used to decide
> > whether a dock station is present...
> > 
> 
> Untested patch attached.
> 
> 
> 

Hi Chuck,
thanks for the patch, this should fix the problem.  Would you care to
resend it with a proper sign-off?

Thanks,
Kristen
-
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/