linux-kernel - Re: multiple bugs

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: <1231687049.17759.12.camel@odie.local>
Date:	Sun, 11 Jan 2009 16:17:29 +0100
From:	Simon Holm Thøgersen <odie@...aau.dk>
To:	w.landgraf@...oo.com
Cc:	linux-kernel@...r.kernel.org
Subject: Re: multiple bugs

(Please use reply-to-all in order not to break threading, it makes it a
 pain for everyone that tries to follow the discussion.)

søn, 11 01 2009 kl. 06:46 -0800, skrev We La:
> 1) More exactly, with all kernels since 2.6.27 -rcX until now, on attempts
> on about 10 machines, I don't get connection or data transfer. Thus I
> think it's not a regression on particular eth drivers, but perhaps on
> the routing or package handling.   On my original message, I gave the
> config for one of these kernels.  Below I give, for comparison, the
> config of 2.6.26.2 with which it still was working.  I have no idea
> which of the differences of the config, or new features, can cause
> this problem.

How do you generate the config for 2.6.27-* and the other versions that
fail? You should normally just use the .config for 2.6.26.2 or whatever
you used last and run 'make oldconfig' selecting the default answer to
each new option unless you have a good reason not to and have read and
understood the help text that goes along with the option. This way you
wouldn't have run into the problem with kernel mode setting either.

And still, even if it is not a problem with a network driver but in
another part of the network layer etc. a bisection run would be a good
way to pinpoint the issue. But see if it is not your config that causes
the problem first.

Simon Holm Thøgersen

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