Re: [PATCH 1/14] i386 / Make write ldt return error code

* Andi Kleen ([email protected]) wrote:
> On Tue, Aug 16, 2005 at 05:06:18PM -0700, Chris Wright wrote:
> > In this case the callers do propagate the error (unless you mean
> > userspace doesn't check return value from syscall, which is same problem
> > if copy_from_user failed, for example).  Xen has done some more wrapping
> 
> Nothing checks them in user space.
> 
> Also how would you handle them anyways? It just doesn't make sense.

Yes, I see your point, although copy_from_user failing has similar issue
if userspace isn't checking errors.  But this one is not critical.

thanks,
-chris
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

---

• References:
  • [PATCH 1/14] i386 / Make write ldt return error code
    • From: [email protected]
  • Re: [PATCH 1/14] i386 / Make write ldt return error code
    • From: Andi Kleen <[email protected]>
  • Re: [PATCH 1/14] i386 / Make write ldt return error code
    • From: Chris Wright <[email protected]>
  • Re: [PATCH 1/14] i386 / Make write ldt return error code
    • From: Andi Kleen <[email protected]>

• Prev by Date: Re: [RFC - 0/9] Generic timekeeping subsystem (v. B5)
• Next by Date: Re: [RFC][PATCH 2.6.13-rc6] add Dell Systems Management Base Driver (dcdbas) with sysfs support
• Previous by thread: Re: [PATCH 1/14] i386 / Make write ldt return error code
• Next by thread: [PATCH] i386 boottime for_each_cpu broken
• Index(es):
  • Date
  • Thread

[Index of Archives]     [Kernel Newbies]     [Netfilter]     [Bugtraq]     [Photo]     [Gimp]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Video 4 Linux]     [Linux for the blind]