> > I thought POSIX made it explicit that you may SIGSEGV or EFAULT at your
> > option. If that SUS rule is stupid, we should just drop it.
> > Performance advantage from MMX-copy-to-user is probably well worth it.
> Stop this STUPID "it speeds things up" argument.
> It's not TRUE.
> We still have to do exactly the same things we do right now, because even
> if we SIGSEGV we still have to return the right number of bytes
> SIGSEGV doesn't mean that the system call wouldn't complete. It removes
> _none_ of the kernel fixup handling, because the SIGSEGV won't be
> delivered until we return to user mode anyway. So please stop mixing these
> two issues up.
If you pass bad pointer to memcpy(), you don't expect any reasonable
return value, right?
So if you pass bad pointer to read(), why would you expect "number of
bytes read" return? Its true that kernel can't simply not return
anything, but giving SIGSEGV and returning -EFAULT seems pretty
reasonable to me. If they really want to, they might extract number of
bytes read from address SIGSEGV occured at [but that's dirty hack, and
people will hopefully realise that and not rely on it].
-- Casualities in World Trade Center: ~3k dead inside the building, cryptography in U.S.A. and free speech in Czech Republic. - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to firstname.lastname@example.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/