linux-kernel - Re: hi, should these code is a problem in nfs system clnt.c?

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] [day] [month] [year] [list]

Date:	Tue, 12 Dec 2006 11:11:45 -0500
From:	Trond Myklebust <trond.myklebust@....uio.no>
To:	Peter Staubach <staubach@...hat.com>
Cc:	linuxer linuxer <tangzt@...oo.com>, linux-kernel@...r.kernel.org,
	torvalds@...l.org, alan@...hat.com
Subject: Re: hi, should these code is a problem in nfs system clnt.c?

On Tue, 2006-12-12 at 09:00 -0500, Peter Staubach wrote:
> linuxer linuxer wrote:
> > Hi, everyone: 
> >     I am a newbie, if my question waste your time, I
> > am sorry for that. 
> >
> >     In clnt.c file ,call_timeout function:    
> >     I suggest the code that judge whether the network
> > link status is down should be added, won't they? 
> >     I tested it with one Ethernet netcard.
> >
> >   
> 
> This would not be a good idea.  What happens if the name of the
> interface used on the system is not "eth0"?
> 
> Also, IP packets can be routed out of any available interface,
> so just because one interface (eth0) is down, doesn't mean
> that the entire system is networkless.

Right. Besides, it is also an obvious layering violation. Idea NAKed.

Trond

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