Perl 6 - the future is here, just unevenly distributed

IRC log for #gluster-dev, 2017-05-24

| Channels | #gluster-dev index | Today | | Search | Google Search | Plain-Text | summary

All times shown according to UTC.

Time Nick Message
01:36 mchangir joined #gluster-dev
01:41 shyam joined #gluster-dev
01:48 ilbot3 joined #gluster-dev
01:48 Topic for #gluster-dev is now Gluster Development Channel - http://gluster.org | For general chat go to #gluster | Patches - http://review.gluster.org/ | Channel Logs - https://botbot.me/freenode/gluster-dev/ & http://irclog.perlgeek.de/gluster-dev/
02:27 jiffin joined #gluster-dev
02:34 vinurs joined #gluster-dev
03:06 Gambit15 joined #gluster-dev
03:22 skoduri joined #gluster-dev
03:28 riyas joined #gluster-dev
03:32 nbalacha_ joined #gluster-dev
03:34 amarts joined #gluster-dev
03:48 itisravi joined #gluster-dev
03:58 PotatoGim Hello! I have a question for 'FREE()' macro code block defined in 'mem-pool.c'. Why do it assign '0xeeeeeeee' to freed variable?
04:18 itisravi PotatoGim: It is just a random but known value. That way when someone accesses it later leading to a segfault, we can be sure that it is a use-after-free scenario. The access would have failed at address 0xeeeeeeee.
04:33 PotatoGim itisravi: Thanks a lot! :)
04:34 itisravi you're welcome :)
04:35 gyadav_ joined #gluster-dev
04:36 gyadav joined #gluster-dev
04:36 ppai joined #gluster-dev
04:44 skumar joined #gluster-dev
04:53 karthik_us joined #gluster-dev
04:54 atinm joined #gluster-dev
05:03 apandey joined #gluster-dev
05:06 jiffin joined #gluster-dev
05:06 karthik_us joined #gluster-dev
05:07 gyadav joined #gluster-dev
05:08 gyadav_ joined #gluster-dev
05:11 sanoj joined #gluster-dev
05:21 ashiq joined #gluster-dev
05:22 Shu6h3ndu joined #gluster-dev
05:24 skoduri joined #gluster-dev
05:24 prasanth joined #gluster-dev
05:25 poornima_ joined #gluster-dev
05:27 rafi1 joined #gluster-dev
05:28 pkalever joined #gluster-dev
05:29 hgowtham joined #gluster-dev
05:32 rafi joined #gluster-dev
05:33 ndarshan joined #gluster-dev
05:44 Saravanakmr joined #gluster-dev
05:44 ankitr joined #gluster-dev
05:46 nishanth joined #gluster-dev
05:48 rastar joined #gluster-dev
05:51 rafi2 joined #gluster-dev
05:52 Humble joined #gluster-dev
05:58 amarts joined #gluster-dev
05:59 itisravi joined #gluster-dev
06:00 apandey_ joined #gluster-dev
06:00 sona joined #gluster-dev
06:02 apandey joined #gluster-dev
06:06 ankitr joined #gluster-dev
06:08 skumar joined #gluster-dev
06:12 kdhananjay joined #gluster-dev
06:25 kotreshhr joined #gluster-dev
06:26 ankitr joined #gluster-dev
07:20 apandey_ joined #gluster-dev
07:22 itisravi_ joined #gluster-dev
07:40 rafi joined #gluster-dev
07:45 kdhananjay joined #gluster-dev
08:30 ankitr joined #gluster-dev
08:37 PotatoGim In libglusterfs/rpc/xdr/src/glusterfs-fops.x:195, What's the meaning of "%#define GF_MAX_LOCK_OWNER_LEN 1024 /* 1kB as per NLM */"? How can it replaced with C macro?
08:45 atinm joined #gluster-dev
08:51 poornima_ joined #gluster-dev
09:13 amarts joined #gluster-dev
09:19 ppai joined #gluster-dev
09:26 annettec joined #gluster-dev
09:41 rafi1 joined #gluster-dev
09:44 atinm joined #gluster-dev
09:47 ankitr joined #gluster-dev
09:47 amarts joined #gluster-dev
09:49 ppai joined #gluster-dev
10:15 ndevos PotatoGim: the % in a .x file cause rpcgen to include this exactly as given in the resulting .c (or  .h?) file
10:16 ndevos PotatoGim: so, the result will have this macro: #define GF_MAX_LOCK_OWNER_LEN 1024 /* 1kB as per NLM */
10:16 PotatoGim ndevos: Thanks a lot! :)
10:17 ndevos PotatoGim: if you want a different macro, it may make sense to use something like '%#include "constants.h"' and place the constants.h in libglusterfs/src or something
10:19 PotatoGim ndevos: Thank you for your advice! I'll keep that in mind! :)
10:20 ndevos PotatoGim: you can check the generated files as well, just run 'make' once, and look in rpc/xdr/src/ afterwards
10:29 amarts joined #gluster-dev
10:36 nishanth joined #gluster-dev
10:47 apandey joined #gluster-dev
11:06 jiffin1 joined #gluster-dev
11:44 gyadav_ joined #gluster-dev
11:44 gyadav joined #gluster-dev
11:46 jiffin1 joined #gluster-dev
11:53 amarts joined #gluster-dev
12:04 Saravanakmr joined #gluster-dev
12:07 kdhananjay joined #gluster-dev
12:22 Saravanakmr_ joined #gluster-dev
12:38 shyam joined #gluster-dev
12:57 Saravanakmr_ joined #gluster-dev
13:06 atai1 joined #gluster-dev
13:08 jiffin1 joined #gluster-dev
13:22 skoduri joined #gluster-dev
13:33 shyam joined #gluster-dev
14:05 kotreshhr left #gluster-dev
14:18 sanoj joined #gluster-dev
14:26 skoduri joined #gluster-dev
14:42 rafi1 joined #gluster-dev
14:43 gyadav joined #gluster-dev
14:43 gyadav_ joined #gluster-dev
14:58 nbalacha_ joined #gluster-dev
15:02 kshlm Community meeting starting now in #gluster-meeting
15:06 wushudoin joined #gluster-dev
15:17 gyadav_ joined #gluster-dev
15:18 gyadav joined #gluster-dev
15:21 shyam joined #gluster-dev
15:33 jiffin joined #gluster-dev
15:41 shyam joined #gluster-dev
15:43 kshlm JoeJulian++ ndevos++
15:43 glusterbot kshlm: JoeJulian's karma is now 9
15:43 glusterbot kshlm: ndevos's karma is now 354
15:43 skumar joined #gluster-dev
15:45 ndevos JoeJulian++ kshlm++
15:45 glusterbot ndevos: JoeJulian's karma is now 10
15:45 glusterbot ndevos: kshlm's karma is now 144
15:46 ndevos JoeJulian: so, Cinder is the component that only takes care of creating/deleting/... the VM-image files, and the actual running is through Nova?
15:46 * ndevos is a real OpenStack noob
15:46 JoeJulian More or less correct.
15:48 misc that's for the 2 first component, now imagine the same, but with 20 others services
15:49 ndevos sure, thats fine, but it doesnt make sense to remove it from a (relatively simple) component, but keep it in others
15:50 ndevos JoeJulian: so, was it removed from Nova as well?
15:53 kshlm ndevos, I still see glusterfs support in the file share service and backup service. It was just the cinder block storage support that was removed.
15:53 ndevos yeah, I just found https://github.com/openstack/nova/blob/master/nova/virt/libvirt/volume/glusterfs.py
15:54 skoduri joined #gluster-dev
15:54 JoeJulian I haven't looked. If you can't manage volumes, support in nova is moot.
15:54 kshlm Maybe with the gluster-block project coming up, we can start with a fresh cinder plugin.
15:55 JoeJulian cinder was the only way to get libgfapi support.
15:55 ankitr joined #gluster-dev
15:55 ndevos right, but it would be more effort to bring back support in Cinder+Nova
15:56 ndevos it doesnt look like Cinder used gfapi at all, but that may not be required, at least Nova can do qemu+gfapi
15:56 Shu6h3ndu joined #gluster-dev
15:58 ndevos kshlm: gluster-block is quite different, it configures iscsi so that applications (containers) can use a block-device
15:58 ndevos kshlm: qemu already knows how to use Gluster through libgfapi, and we're maintaining that well
15:58 ndevos ... *well* in the sense that we try, and send and review patches for it
16:01 Saravanakmr joined #gluster-dev
16:08 atai1 left #gluster-dev
16:23 amarts joined #gluster-dev
16:26 Gambit15 joined #gluster-dev
16:29 jiffin joined #gluster-dev
16:45 gyadav joined #gluster-dev
16:46 gyadav_ joined #gluster-dev
16:50 Humble joined #gluster-dev
16:52 vinurs joined #gluster-dev
16:58 ankitr joined #gluster-dev
17:01 nbalacha_ joined #gluster-dev
17:05 shaunm joined #gluster-dev
17:06 gyadav_ joined #gluster-dev
17:06 gyadav joined #gluster-dev
17:33 ankitr joined #gluster-dev
17:43 skumar joined #gluster-dev
17:48 jiffin joined #gluster-dev
17:49 rafi joined #gluster-dev
17:54 rafi joined #gluster-dev
18:01 ashiq joined #gluster-dev
18:12 gyadav_ joined #gluster-dev
18:13 gyadav joined #gluster-dev
18:17 rafi1 joined #gluster-dev
18:24 pranithk1 joined #gluster-dev
18:33 rafi joined #gluster-dev
20:39 shyam joined #gluster-dev

| Channels | #gluster-dev index | Today | | Search | Google Search | Plain-Text | summary