| 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
| ||
|
Message-ID: <AANLkTikVvaiqsj=ZiW4kN-CQB=oTuYpQQGH6+v6ZY1ny@mail.gmail.com> Date: Fri, 14 Jan 2011 19:52:27 +1100 From: Nick Piggin <npiggin@...il.com> To: Miklos Szeredi <miklos@...redi.hu> Cc: linux-fsdevel@...r.kernel.org, linux-kernel@...r.kernel.org Subject: Re: Important for fs devs: rcu-walk merged upstream On Fri, Jan 14, 2011 at 7:45 PM, Miklos Szeredi <miklos@...redi.hu> wrote: > On Fri, 14 Jan 2011, Nick Piggin wrote: >> On Fri, Jan 14, 2011 at 3:18 AM, Miklos Szeredi <miklos@...redi.hu> wrote: >> Surely you'd need some filtering anyway? I don't think any function >> involving path lookup could sanely return -ECHILD. > > No, but not filtering doesn't normally hurt. And it's not quite > trivial deciding what should be allowed and what shoudln't, and the > filter would have to be updated for each addition of a new errno. So > I'm not sure I want to go there. Well if you allow untrusted filesystems it is possible that -ECHILD return will do something a bit silly. So it would be good to filter it I guess. >> That said, it probably is a good idea to have a new errno. > > Yeah, that makes the fitering much easier. How so? Would -ECHILD ever be sane to return? I'm not arguing against changing it but I just want to know what the issue is there. -- 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/
Powered by blists - more mailing lists