linux-kernel - Re: Issue building kernel driver

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]

Message-Id: <1193940217.7555.13.camel@localhost>
Date:	Thu, 01 Nov 2007 13:03:37 -0500
From:	Chris Holvenstot <cholvenstot@...cast.net>
To:	Adrian Bunk <bunk@...nel.org>,
	kernel list <linux-kernel@...r.kernel.org>
Subject: Re: Issue building kernel driver

Thank you for the quick response - normally I would not have bothered
with the kernel list but this is a case where the same source would
sucessfully compile on "git4" but not on "git9 or git10"

As I previously stated the message is also being sent to the VirtualBox
developers (who will likely tell that they don't support those who build
and test development kernels)

Once again thanks





On Thu, 2007-11-01 at 18:51 +0100, Adrian Bunk wrote:
> On Thu, Nov 01, 2007 at 12:39:06PM -0500, Chris Holvenstot wrote:
> > Adrian Bunk <bunk@...nel.org>Adrian Bunk <bunk@...nel.org>
> > Although it may not be popular with the crowd here, I do have a valid
> > reason to run Windows - and I accomidate this using the VirtualBox
> > product.  
> > http://www.google.com/
> > Since I try to be slightly useful and build as many of the "test" kernel
> > images I can I end up rebuilding the VirtualBox kernel driver (open
> > source) on an almost daily basis.
> >...
> > I am not sure if this should be reported to the kernel folks or the
> > VirtualBox folks - but the kernel code is what changed.  However I will
> > post this on the VirtualBox forum too.
> 
> We had a (different) bug report involving exactly this external driver 
> at some older post 2.6.23 kernel where it turned out it was a problem in 
> this driver - and this one also looks really like a problem in their 
> driver.
> 
> Generally, problems with external drivers should be reported to the 
> vendors of these drivers and not here (unless it's clear it's a bug in 
> the kernel and not in the driver).
> 
> > Thanks
> 
> cu
> Adrian
> 

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