Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > linux.kernel > #1467222 > unrolled thread

Re: [Xen-devel] [PATCH] xenbus: don't BUG() on user mode induced condition

Started bySylvain Munaut <s.munaut@whatever-company.com>
First post2016-08-21 21:40 +0200
Last post2016-08-22 09:30 +0200
Articles 3 — 2 participants

Back to article view | Back to linux.kernel

This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by below is the oldest one visible, not the original post.


Contents

  Re: [Xen-devel] [PATCH] xenbus: don't BUG() on user mode induced condition Sylvain Munaut <s.munaut@whatever-company.com> - 2016-08-21 21:40 +0200
    Re: [Xen-devel] [PATCH] xenbus: don't BUG() on user mode  induced condition "Jan Beulich" <JBeulich@suse.com> - 2016-08-22 08:50 +0200
      Re: [Xen-devel] [PATCH] xenbus: don't BUG() on user mode induced condition Sylvain Munaut <s.munaut@whatever-company.com> - 2016-08-22 09:30 +0200

#1467222 — Re: [Xen-devel] [PATCH] xenbus: don't BUG() on user mode induced condition

FromSylvain Munaut <s.munaut@whatever-company.com>
Date2016-08-21 21:40 +0200
SubjectRe: [Xen-devel] [PATCH] xenbus: don't BUG() on user mode induced condition
Message-ID<s8GL9-4yb-47@gated-at.bofh.it>
Hi,

> --- 4.7-rc6-xen.orig/drivers/xen/xenbus/xenbus_dev_frontend.c
> +++ 4.7-rc6-xen/drivers/xen/xenbus/xenbus_dev_frontend.c
> @@ -316,11 +316,18 @@ static int xenbus_write_transaction(unsi
>                         rc = -ENOMEM;
>                         goto out;
>                 }
> +       } else {
> +               list_for_each_entry(trans, &u->transactions, list)
> +                       if (trans->handle.id == u->u.msg.tx_id)
> +                               break;
> +               if (&trans->list == &u->transactions)
> +                       return -ESRCH;
>         }

Shouldn't there be some tolerance in there in case the tx_id is zero ?
(i.e. no transaction).

I'm trying to find out why just doing "xenstore-ls" doesn't work on my
4.4.20 kernel and when stracing it, I see it doing :

access("/dev/xen/xenbus", F_OK)         = 0
stat("/dev/xen/xenbus", {st_mode=S_IFCHR|0600, st_rdev=makedev(10,
60), ...}) = 0
open("/dev/xen/xenbus", O_RDWR)         = 3
brk(0)                                  = 0x18e4000
brk(0x1905000)                          = 0x1905000
rt_sigaction(SIGPIPE, {SIG_IGN, [], SA_RESTORER, 0x7fe4dd98e0e0},
{SIG_DFL, [], 0}, 8) = 0
write(3, "\1\0\0\0\0\0\0\0\0\0\0\0\2\0\0\0", 16) = 16
write(3, "/\0", 2)                      = -1 ESRCH (No such process)


So either what xenstore-ls does is invalid, or that condition
requiring a transaction is too strict.

Or am I missing something here ?


Cheers,

    Sylvain Munaut

[toc] | [next] | [standalone]


#1467394 — Re: [Xen-devel] [PATCH] xenbus: don't BUG() on user mode induced condition

From"Jan Beulich" <JBeulich@suse.com>
Date2016-08-22 08:50 +0200
SubjectRe: [Xen-devel] [PATCH] xenbus: don't BUG() on user mode induced condition
Message-ID<s8Rdw-2H5-3@gated-at.bofh.it>
In reply to#1467222
>>> On 21.08.16 at 21:36, <s.munaut@whatever-company.com> wrote:
>> --- 4.7-rc6-xen.orig/drivers/xen/xenbus/xenbus_dev_frontend.c
>> +++ 4.7-rc6-xen/drivers/xen/xenbus/xenbus_dev_frontend.c
>> @@ -316,11 +316,18 @@ static int xenbus_write_transaction(unsi
>>                         rc = -ENOMEM;
>>                         goto out;
>>                 }
>> +       } else {
>> +               list_for_each_entry(trans, &u->transactions, list)
>> +                       if (trans->handle.id == u->u.msg.tx_id)
>> +                               break;
>> +               if (&trans->list == &u->transactions)
>> +                       return -ESRCH;
>>         }
> 
> Shouldn't there be some tolerance in there in case the tx_id is zero ?
> (i.e. no transaction).
> 
> I'm trying to find out why just doing "xenstore-ls" doesn't work on my
> 4.4.20 kernel and when stracing it, I see it doing :
> 
> access("/dev/xen/xenbus", F_OK)         = 0
> stat("/dev/xen/xenbus", {st_mode=S_IFCHR|0600, st_rdev=makedev(10,
> 60), ...}) = 0
> open("/dev/xen/xenbus", O_RDWR)         = 3
> brk(0)                                  = 0x18e4000
> brk(0x1905000)                          = 0x1905000
> rt_sigaction(SIGPIPE, {SIG_IGN, [], SA_RESTORER, 0x7fe4dd98e0e0},
> {SIG_DFL, [], 0}, 8) = 0
> write(3, "\1\0\0\0\0\0\0\0\0\0\0\0\2\0\0\0", 16) = 16
> write(3, "/\0", 2)                      = -1 ESRCH (No such process)
> 
> 
> So either what xenstore-ls does is invalid, or that condition
> requiring a transaction is too strict.
> 
> Or am I missing something here ?

See https://patchwork.kernel.org/patch/9281193/.

Jan

[toc] | [prev] | [next] | [standalone]


#1467419

FromSylvain Munaut <s.munaut@whatever-company.com>
Date2016-08-22 09:30 +0200
Message-ID<s8RQd-3fx-25@gated-at.bofh.it>
In reply to#1467394
Hi Jan,

> See https://patchwork.kernel.org/patch/9281193/.

Thanks for the pointer !

I had checked the kernel git tree for a potential fix, but didn't
think of patchwork.


Cheers,

    Sylvain Munaut

[toc] | [prev] | [standalone]


Back to top | Article view | linux.kernel


csiph-web