search for: goto

...ystem would be good. Better still would be an automated cocci script. The existing checkpatch test for UNNECESSARY_BREAK has a few too many false positives. >From a script run on next on July 28th: arch/arm/mach-s3c24xx/mach-rx1950.c:266: WARNING:UNNECESSARY_BREAK: break is not useful after a goto or return arch/arm/nwfpe/fpa11_cprt.c:38: WARNING:UNNECESSARY_BREAK: break is not useful after a goto or return arch/arm/nwfpe/fpa11_cprt.c:41: WARNING:UNNECESSARY_BREAK: break is not useful after a goto or return arch/mips/include/asm/mach-au1x00/au1000.h:684: WARNING:UNNECESSARY_BREAK: break is n...

...========================= [mainmenu] ; ; Answer the phone and play the main menu option ; include => default exten => s,1,Answer exten => s,2,AGI(schedule.agi) exten => s,3,Background(fti_welcome) exten => s,4,Background(fti_menu_options_changed) exten => s,5,GotoIf($[${STATUS} = closed]?9:6) exten => s,6,GotoIf($[${STATUS} = shortday]?11:7) exten => s,7,GotoIf($[${STATUS} = holiday]?11:8) exten => s,8,GotoIf($[${STATUS} = weekend]?13:15) exten => s,9,Background(fti_closed_evening) ; STATUS=closed exten => s,10,Goto(s,15) exten => s,11,B...

...AIT 120 SET SIPDOMAIN "sip.mycompany.com" SET SIPPROXYSRVR "204.140.111.219" SET SIPPORT "5070" (this is not a typo) SET SIPREGISTRAR "204.140.111.219" SET SP_DIRSRVR 10.1.1.1 SET SP_DIRSRVRPORT 389 SET SP_DIRTOPDN ou=People,o=avaya.com IF $MODEL4 SEQ 4602 goto SETTINGS4602 IF $MODEL4 SEQ 4610 goto SETTINGS4610 IF $MODEL4 SEQ 4620 goto SETTINGS4620 IF $MODEL4 SEQ 4621 goto SETTINGS4621 IF $MODEL4 SEQ 4622 goto SETTINGS4622 IF $MODEL4 SEQ 4625 goto SETTINGS4625 IF $MODEL4 SEQ 4630 goto SETTINGS4630 goto END goto END SET WMLHOME http://support.avaya.com/elm...

...calloc (1, sizeof *ret); + if (ret == NULL) { + reply_with_error ("calloc"); + return NULL; + } + + for (i = 0; lines[i] != NULL; ++i) { + if (p = strstr (lines[i], "meta-data=")) { + ret->mntpoint = split_strdup (p + 10); + if (ret->mntpoint == NULL) goto error; + } else if (p = strstr (lines[i], "isize=")) { + buf = split_strdup (p + 6); + if (buf == NULL) goto error; + if (parse_uint32 (&ret->inodesize, buf) == -1) + goto error; + } else if (p = strstr (lines[i], "agcount=")) { + buf = sp...

OpenSSH Developers, I'm researching whether or not OpenSSH is a viable commercial alternative to F-SECURE SSH or SSH.COM's ssh, but I'm not getting the kind of results that I expected from a "Non patent encumbered ssh client". When I attempt to build OpenSSH against an OpenSSL build without rc5, idea, or rsa it bombs since OpenSSL doesn't place the header files in the

...for an example #include extensions_custom.conf [from-trunk] ; just an alias since VoIP shouldn't be called PSTN include => from-pstn [from-pstn] include => from-pstn-custom ; create this context in extensions_custom.conf to include customizations include => ext-did ;exten => fax,1,Goto(ext-fax,in_fax,1) exten => _.,1,Wait(1) exten => _.,2,Goto(from-pstn,s,1) var/log/asterisk/full (when recieving a call from pstn): Apr 26 18:43:33 VERBOSE[2696] logger.c: -- Remote UNIX connection Apr 26 18:43:52 VERBOSE[25804] logger.c: -- Remote UNIX connection disconnected Apr 26 18:44:5...

Anyone know how to let asterisk deal with the progress codes coming from the carrier? The problem I am having is when a customer calls an invalid number the carrier tells me the call is invalid via a progress code but doesn't route me to a recording (this number is invalid). Instead they hang up on me causing a fast busy or sometimes hold up the call with dead air for 15 to 30 seconds then a

I've not seen an answer to this in any forum. I make a call through Asterisk, with a VOIP phone, doesn't matter which. The call gets made, I leave a voicemail, or complete the call in some manner, and the other side hangs up. I hear a busy signal on the phone on my end. If I have an extension that looks like this, after the hangup() is executed, my phone gives busy signals until I

...er? > > -- > Matt Fleming, Intel Open Source Technology Center > Maybe this (simpler and first) cfg is enough for testing: *** START SYSLINUX.CFG 1 *** UI menu.c32 PROMPT 0 MENU CLEAR MENU BEGIN 0000 LABEL - MENU DEFAULT MENU LABEL [ ] Persistent changes MENU GOTO 1000 MENU END MENU BEGIN 1000 LABEL - MENU DEFAULT MENU LABEL [*] Persistent changes MENU GOTO 0000 MENU END *** END SYSLINUX.CFG 1 *** The next (second) step would be something like: *** START SYSLINUX.CFG 2 *** UI menu.c32 PROMPT 0 MENU CLEAR MENU BEGIN...

...allback(struct rcu_head *head) { struct inode *inode = container_of(head, struct inode, i_rcu); diff --git a/fs/btrfs/super.c b/fs/btrfs/super.c index 2bdaafd..db591e8 100644 --- a/fs/btrfs/super.c +++ b/fs/btrfs/super.c @@ -1802,6 +1802,9 @@ static int btrfs_run_sanity_tests(void) if (ret) goto out; ret = btrfs_test_extent_io(); + if (ret) + goto out; + ret = btrfs_test_inodes(); out: btrfs_destroy_test_fs(); return ret; diff --git a/fs/btrfs/tests/btrfs-tests.c b/fs/btrfs/tests/btrfs-tests.c index 697d527..757ef00 100644 --- a/fs/btrfs/tests/btrfs-tests.c +++ b/fs/btrfs/tests/btr...

> http://www.voip-info.org/wiki/index.php?page=Asterisk+cmd+Goto > > show application goto > > -= Info about application 'Goto' =- > > [Synopsis] > Jump to a particular priority, extension, or context > > [Description] > Goto([[context|]extension|]priority): This application will cause the > calling channel to cont...

...om> */ #include <linux/kernel.h> +#include <linux/sched.h> +#include <linux/wait.h> #include <linux/mm.h> #include <linux/slab.h> #include <linux/module.h> @@ -243,11 +245,7 @@ int vmbus_open(struct vmbus_channel *newchannel, u32 send_ringbuffer_size, goto errorout; } - openInfo->waitevent = osd_waitevent_create(); - if (!openInfo->waitevent) { - err = -ENOMEM; - goto errorout; - } + init_waitqueue_head(&openInfo->waitevent); openMsg = (struct vmbus_channel_open_channel *)openInfo->msg; openMsg->header.msgtype = CHANNEL...

...om> */ #include <linux/kernel.h> +#include <linux/sched.h> +#include <linux/wait.h> #include <linux/mm.h> #include <linux/slab.h> #include <linux/module.h> @@ -243,11 +245,7 @@ int vmbus_open(struct vmbus_channel *newchannel, u32 send_ringbuffer_size, goto errorout; } - openInfo->waitevent = osd_waitevent_create(); - if (!openInfo->waitevent) { - err = -ENOMEM; - goto errorout; - } + init_waitqueue_head(&openInfo->waitevent); openMsg = (struct vmbus_channel_open_channel *)openInfo->msg; openMsg->header.msgtype = CHANNEL...

...sers WHERE confid='${SQL_ESC(${CONF_ID})}' extensions.conf section: [infromhost] ;Host dials 8888 over SIP trunk exten=8888,1,Answer exten=8888,n,Background(conf-getconfno) exten=8888,n,WaitExten(10) exten=8888,n,Hangup exten=_XXXXXX,1,Set(GLOBAL(CONF_ID)=${EXTEN}) exten=_XXXXXX,n,GoTo(rooms,${EXTEN},1) ; [rooms] exten=_XXXXXX,1,Set(CONF_ID=${EXTEN}) exten=_XXXXXX,n,Background(conf-getpin) exten=_XXXXXX,n,WaitExten(5) exten=_XXXXXX,n,Hangup exten=_1XXXXX,1,Goto(getpin,${EXTEN},1) exten=_2XXXXX,1,Goto(getpin,${EXTEN},1) exten=_3XXXXX,1,Goto(getpin,${EXTEN},1) exten=_4XXX...

...about how "the programmer >>>>> knows what they're doing". Perhaps I'm being too cavalier here? My concern, >>>>> if you want to call it that, is that we don't be too restrictive on the new >>>>> behavior. For example, the "asm goto" may set a register to an error value >>>>> (made up on the spot; may not be a common use). But, if there's no real >>>>> reason to have the value be valid on the abnormal path, then sure we can >>>>> declare that it's not valid on the abnor...

...uot;the programmer >>>>>> knows what they're doing". Perhaps I'm being too cavalier here? My concern, >>>>>> if you want to call it that, is that we don't be too restrictive on the new >>>>>> behavior. For example, the "asm goto" may set a register to an error value >>>>>> (made up on the spot; may not be a common use). But, if there's no real >>>>>> reason to have the value be valid on the abnormal path, then sure we can >>>>>> declare that it's not valid...

....c > +++ b/drivers/net/virtio_net.c > @@ -833,14 +833,14 @@ static int virtnet_xdp_handler(struct bpf_prog *xdp_prog, struct xdp_buff *xdp, > stats->xdp_tx++; > xdpf = xdp_convert_buff_to_frame(xdp); > if (unlikely(!xdpf)) > - return VIRTNET_XDP_RES_DROP; > + goto drop; > > err = virtnet_xdp_xmit(dev, 1, &xdpf, 0); > if (unlikely(!err)) { > xdp_return_frame_rx_napi(xdpf); > } else if (unlikely(err < 0)) { > trace_xdp_exception(dev, xdp_prog, act); > - return VIRTNET_XDP_RES_DROP; > + goto drop; >...

...y of handling the error codes properly....? Asterisk version: 1.4.22.1 Libpri: 1.4.10.1 dahdi: 2.2.0.2 are the versions that I am using. The way I was handling the codes for the server 2: [macro-result] exten => s,1,Wait(1) exten => s,2,ResetCDR(w) exten => s,3,NoCDR() exten => s,4,GotoIf($[${ISNULL(${ARG1})}]?7:5) exten => s,5,Set(RC=${ARG1}) exten => s,6,Goto(s|9) exten => s,7,GotoIf($[${ISNULL(${DIALSTATUS})}]?8:rc-${DIALSTATUS}|1) exten => s,8,Set(RC=${IF($[${ISNULL(${HANGUPCAUSE})}]?0:${HANGUPCAUSE})}) exten => s,9,Goto(rc-${RC}|1) exten => s,10,Hangup(${RC}...

...8a 100644 --- a/drivers/net/virtio_net.c +++ b/drivers/net/virtio_net.c @@ -833,14 +833,14 @@ static int virtnet_xdp_handler(struct bpf_prog *xdp_prog, struct xdp_buff *xdp, stats->xdp_tx++; xdpf = xdp_convert_buff_to_frame(xdp); if (unlikely(!xdpf)) - return VIRTNET_XDP_RES_DROP; + goto drop; err = virtnet_xdp_xmit(dev, 1, &xdpf, 0); if (unlikely(!err)) { xdp_return_frame_rx_napi(xdpf); } else if (unlikely(err < 0)) { trace_xdp_exception(dev, xdp_prog, act); - return VIRTNET_XDP_RES_DROP; + goto drop; } *xdp_xmit |= VIRTIO_XDP_TX; @@ -850,7 +8...

commit commit ea04036032edda6f771c1381d03832d2ed0f6c31 ("CodingStyle: add some more error handling guidelines") suggests never naming goto labels after the goto location - that is the error that is handled. But it's actually pretty common and IMHO it's a reasonable style provided each error gets its own label, and each label comes after the matching cleanup: foo = kmalloc(SIZE, GFP_KERNEL); if...