netdev - Re: rhashtable issue

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: <dhgvxsvugfqrowuypzwizy5psdfm4fy5xveq2fuepqfmhdlv5e@pj5kt4pmansq>
Date: Mon, 25 Nov 2024 22:51:04 -0500
From: Kent Overstreet <kent.overstreet@...ux.dev>
To: Herbert Xu <herbert@...dor.apana.org.au>
Cc: NeilBrown <neilb@...e.de>, Thomas Graf <tgraf@...g.ch>, 
	netdev@...r.kernel.org
Subject: Re: rhashtable issue - -EBUSY

On Tue, Nov 26, 2024 at 11:14:41AM +0800, Herbert Xu wrote:
> On Mon, Nov 25, 2024 at 10:12:44PM -0500, Kent Overstreet wrote:
> >
> > Does the knob have to be insecure_elasticity? Neal's idea of just
> > blocking instead of returning -EBUSY seems perfectly viable to me, most
> > uses I'm aware of don't need insertions to be strictly nonblocking.
> 
> Well having a knob is not negotiable because we must have this
> defence for networking users where hostile actors are a fact of
> life.
> 
> And no you cannot block in networking.

I just meant having a knob that's called "insecure". Why not a knob
that selects nonblocking vs. reliable?