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] [thread-next>] [day] [month] [year] [list]
Message-ID: <20091221163843.GB3529@gibson.comsick.at>
Date:	Mon, 21 Dec 2009 17:38:43 +0100
From:	Michael Guntsche <mike@...loops.com>
To:	Kumar Gopalpet-B05799 <B05799@...escale.com>
Cc:	netdev <netdev@...r.kernel.org>
Subject: Re: [BUG] 2.6.33-rc1 gianfar error message

On 21 Dec 09 14:19, Kumar Gopalpet-B05799 wrote:
> Michael, 
> 
> Kindly try the following changes at your side and let me know the
> results. I couldn't test this
> as I don't have any TSEC device with me.
<snip>

Your patch did not apply to vanilla 2.6.32-rc1 at all. I patched the
code myself and up to now I do not see any error messages. Uptime is at
33 minutes, without the patch the error message appeared immediately
after booting.

Just for my understanding. Is the first diff part of the fix as well?
With this change the FCB is only removed if there are padded bytes, why
would this make a difference here?

Kind regards,
Michael
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ