devel February 2014

devel@lists.centos.org

43 participants
32 discussions

VoIP SIG Hangout on Feb 13, 16:00 UTC
by Patrick Laimbock 08 Feb '14

08 Feb '14

Hi, The VoIP SIG Hangout has been rescheduled and will now take place on Feb 13 at 16:00 UTC [0]. For more information how to join the hangout on Google+ or follow it on Youtube please check http://wiki.centos.org/OfficeHours Nothing set in stone but some of the things open for discussion are the scope of the VoIP SIG, the goal, the target audience, the deliverables, content distribution and lets not forget the actual proposal. It's also helpful to get an industry perspective, how to make the production side easier and facilitate processes that improve the usability of CentOS in the VoIP sector. Best regards, Patrick Laimbock [0] http://www.timeanddate.com/worldclock/fixedtime.html?iso=20140213T16&am=30

2 1

GSoC mentoring org application, and 14 Feb deadline [GSoC]
by Karsten Wade 07 Feb '14

07 Feb '14

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi: I'm in the mode of "perfect is enemy of good enough", so I'm going to send out a status right now before I keep waiting to get more done. :) A handful of people have offered some help, project ideas, and to be the co-/backup admin (an application requirement.) Thanks! Our main needs to complete our application are: * Ideas, ideas, ideas - SIGs take note! * A backup admin * Mentors (and teams) beginning to commit Please read on for current status on everything: ideas, mentors, office hours, backup admin, and students. == Ideas We need good ideas, and around one mentor for each idea. (It's OK if we have a few more ideas than mentors assigned right now, as long as the idea list is long enough. It's job is to give students ideas on what and how to write their proposals.) http://wiki.centos.org/GSoC/2014/Ideas If you have an idea, fill out the template, or email it to me. If you think it needs a bit of discussion first, you can start a thread for it on centos-devel. SIGs -- this is a great way to get work done toward your variant needs. Packaging, yum plugins, and so forth are all good approaches. It's fine (and encouraged) if the students' work ends up happening primarily in your upstream and we absorb the goodness in to CentOS Linux later. == Mentors You are needed, at least one for each student. You can represent a group, such as release engineering, QA, or a SIG. The rest of your group should be prepared to work with the students on proposals and the final project. == CentOS Office Hours We'll use the Monday CentOS Office Hours to talk about GSoC: http://wiki.centos.org/OfficeHours That's at 16:00 UTC on a Google Hangout and live on YouTube or via http://www.centos.org/media. At the moment it will be any of the Board members chatting about things, but we may have room for a few other voices if there is someone else we should include in the discussion. == Backup admin & administrivia I'm working the application details here: http://wiki.centos.org/GSoC/2014/Application We need a backup admin, it's mandatory for the application. I've heard from a few interested folks, please let me know if you are interested. I'd especially like to work with someone who hasn't administered GSoC before, so I can spread the knowledge. We can have more than one backup admin, but we definitely need one for the application. Since I'm so new to the community, I'm going to consult the rest of the Board members for who would make good co-/backup-admins. I'll try to get that figured out early next week, let's set Tuesday end-of-day in California for that. We also need some tags to associate with the project, such as: Linux, yum, RPM, packaging, OpenStack, Ceph, Python, etc. Suggestions welcome. == Students Your time to apply hasn't come yet. We need to be accepted as a mentoring org first. But it is a great thing when existing community members who are also students apply for the projects. I've seen quite a number of very good results from that - getting paid to spend the summer making CentOS Linux or the Project better! - - Karsten - -- Karsten 'quaid' Wade .^\ CentOS Doer of Stuff http://TheOpenSourceWay.org \ http://community.redhat.com @quaid (identi.ca/twitter/IRC) \v' gpg: AD0E0C41 -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iEYEARECAAYFAlL1anYACgkQ2ZIOBq0ODEGgMgCglTM4oreC0DBOahsEc3iJ4jX9 o4AAoIw5ivDA8C99YRHnL4OH/ic7R/RX =/nEN -----END PGP SIGNATURE-----

1 0

ClearCenter Marketplace for CentOS Variant
by David Loper 07 Feb '14

07 Feb '14

ClearCenter and ClearFoundation are interested in starting a CentOS variant called 'ClearCenter Marketplace for CentOS'. This will allow management of various CentOS services, EPEL packages, and third party applications to be easily managed and configured under CentOS. We are also interested in being part of a SIG centered around 'Server Management.' Please let us know the next steps. We'd like to get started right away and we are willing to participate in the process of helping to set up shop. Let us know how we can serve. -- David Loper President, ClearFoundation

4 10

CentOS-6.5 support for the "Ekoore Python3v2 TOUCHPANEL added using 2 patches.
by Sebastian Yarici 07 Feb '14

07 Feb '14

hi'lo #centOS-devel, we added support to CentOS6.5 for the Tablet-PC "EKOORE Python3v2" it took us some time but we have a fix! one change to the kernel-config and one change to the FDI file, please tell me how to contribute the two changes. greetingz --c11

2 1

VoIP SIG
by Rob Thomas 06 Feb '14

06 Feb '14

I'd like to put my hand up to be part of the VoIP SIG. After mentioning this in IRC, I've also had two other people contact me privately (puzzled and JHogarth) with their interest too. Currently we (FreePBX) build 'FreePBX Distro', which is a up-to-date CentOS distro, with a couple of known-broken packages upgraded (drbd, pacemaker) or replaced (asterisk). --Rob

7 15

proposal on process to carry distro package patches
by Karanbir Singh 05 Feb '14

05 Feb '14

hi, https://git.centos.org/tree/sig-core!bld-seven.git mirrored at : https://github.com/CentOS/sig-core-bld-seven now carries a proposed process to carry package patches. So stuff like branding or build changes needed, or even content changes to make things work could be carried like this. Primary target is for people doing arch work that isnt inherited from upstream. Comments welcome, were only going to start with this for the i686 builds, but if it works and is acceptable widely, we can roll this out across the board. - KB -- Karanbir Singh +44-207-0999389 | http://www.karan.org/ | twitter.com/kbsingh GnuPG Key : http://www.karan.org/publickey.asc

2 2

Repository structures for SIG and variants in the future
by Jim Perrin 05 Feb '14

05 Feb '14

As part of opening up the possibilities for SIGs and Variants within the CentOS ecosystem, we need to give some thought to how repositories should be structured so that different can cooperate with each other. What we have discussed in the past, and what I'd like to propose to the -devel community, is that we adopt a page similar to the KDE framework. The way I envision this working is as follows: - Tier 1 repositories: Adds packages only. These repos may not update or replace anything in the core distribution. (Example: EPEL) - Tier 2 repositories: These repositories may provide provide packages that update or otherwise enhance packages in the base distribution, but otherwise maintain compatibility. (Example IUS - Tier 3 repositories: These repositories contain packages that conflict with software inside the core distribution. This would be Xen4CentOS for example, which replaces the kernel, and adds in xen functionality. Each tier may choose to rely on dependencies from repositories in the tier above it, but not the other way around. For example, the tier 3 Xen4 repository could choose to rely on packages from a tier1 like EPEL, or a tier2 like IUS. However a tier1 or tier2 could not rely on a tier3. A good real-world example of this would be rpmfusion's dependence on the EPEL repository. The other aspect of this that needs to be discussed is package duplication. For example, several of the proposed SIGs have some overlap in their packages. Would the preference here be that each SIG/Variant maintain their own version of the package, or should there be a common package set established? Both methods fit into the model described above, and both have pros/cons associated. What does the community think about this? -- Jim Perrin The CentOS Project | http://www.centos.org twitter: @BitIntegrity | GPG Key: FA09AD77

11 51

Centos 7 and powerpc
by Bryson Lee 04 Feb '14

04 Feb '14

Hi, Would it be possible to get some insight into the prospects for PowerPC support in Centos 7? We deliver an application on IBM Power7 servers that's currently built atop a fairly heavily customized Fedora 12 distro. We anticipate having to move our platform forward at some point, if for no other reason than keeping up with whatever IBM does in terms of hardware evolution. We also have a vested interest in the ppc64 / ppc32 question, since our app is somewhat bound into the 32-bit arch and the 64-bit kernel / 32-bit userland structure we inherit from F12. We have a small number of PS710's in-house, and will probably get at least one of whatever winds up being the equivalent Power8 machine as soon as it becomes available. I'm not in a position to be able to expose a build node to the outside world, but I can certainly build /install / test internally and do some troubleshooting. Any info that can be shared at this point? Any way I can help? Thanks, -Bryson Lee ________________________________ Please note that my e-mail address has changed. My new (current) address is Bryson.Lee(a)sslmda.com. ________________________________ This message (including any attachments) may contain confidential information intended for a specific individual and purpose. If you are not the intended recipient, you should delete this message and any attachments.

3 3

SIG reps syncing often
by Karanbir Singh 04 Feb '14

04 Feb '14

hi, >From the fosdem conversations.. it was clear that for cross SIG co-operation to work we are going to need to have a SIG's syncup every so often. And we could / should have something like : the CentOS Board is responsible for setting up and running a SIG's syncup once a month, with the SIG representatives optionally required to come themselves or nominate someone else ( again optionally ) to come along. This could be a hangout, a conf call ( go Voip SIG! ), or an irc chat. thoughts ? - KB -- Karanbir Singh +44-207-0999389 | http://www.karan.org/ | twitter.com/kbsingh GnuPG Key : http://www.karan.org/publickey.asc

1 0

Kernel OOPS (NULL pointer) with incomplete sock structure?
by Andrew Smith 03 Feb '14

03 Feb '14

I'm debugging a problem that has appeared on a test rig here and I'm wondering if anybody could shed any additional insight into what might be happening. I have a rig running on VMWare ESXi 5.5 with 12 4 Core CentOS 6.4 shipping approximately 100MB/second across the network and within an hour usually one of the nodes fails with a trap as follows. <7>out of order segment: rcv_next 3F89F4D seq AF008380 - A5BE3000 <1>BUG: unable to handle kernel NULL pointer dereference at 00000000000000b0 <1>IP: [<ffffffff8148fd63>] skb_set_owner_r+0x53/0x70 <4>PGD 13ba5a067 PUD 13cec4067 PMD 0 <4>Oops: 0000 [#1] SMP <4>last sysfs file: /sys/module/ip_tables/initstate <4>CPU 0 <4>Modules linked in: iptable_mangle ipv6 ipt_REJECT nf_conntrack_ipv4 nf_defrag_ipv4 xt_state nf_conntrack iptable_filter ip_tables ppdev parport_pc parport vmxnet(U) vmware_balloon vmci(U) i2c_piix4 i2c_core sg shpchp ext4 mbcache jbd2 sd_mod crc_t10dif sr_mod cdrom vmw_pvscsi pata_acpi ata_generic ata_piix dm_mirror dm_region_hash dm_log dm_mod [last unloaded: scsi_wait_scan] <4> <4>Pid: 1329, comm: java Not tainted 2.6.32-358.11.1.el6.x86_64 #1 VMware, Inc. VMware Virtual Platform/440BX Desktop Reference Platform <4>RIP: 0010:[<ffffffff8148fd63>] [<ffffffff8148fd63>] skb_set_owner_r+0x53/0x70 <4>RSP: 0000:ffff880028203a30 EFLAGS: 00010206 <4>RAX: 0000000000000000 RBX: ffff8800a405f780 RCX: 0000000000000000 <4>RDX: 0000000000000ab4 RSI: ffff8800a405f780 RDI: ffff8800a405f780 <4>RBP: ffff880028203a40 R08: 00000000000126a8 R09: 00000000fffffff7 <4>R10: 0000000000000007 R11: 000000000000000a R12: ffff8800a405f780 <4>R13: ffff8800a405f780 R14: ffff8800a405fd00 R15: 0000000000000002 <4>FS: 00007ff42d0d0700(0000) GS:ffff880028200000(0000) knlGS:0000000000000000 <4>CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 <4>CR2: 00000000000000b0 CR3: 000000013c441000 CR4: 00000000000006f0 <4>DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 <4>DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400 <4>Process java (pid: 1329, threadinfo ffff8800a5596000, task ffff880139c94080) <4>Stack: <4> ffff8800a405f780 ffff8800a405f780 ffff880028203a60 ffffffff814950f2 <4><d> ffff8800a405f780 0000000000000004 ffff880028203a80 ffffffff8143d38e <4><d> 0000000000000000 ffff8800af008380 ffff880028203b50 ffffffff81496dd4 <4>Call Trace: <4> <IRQ> <4> [<ffffffff814950f2>] tcp_data_queue+0x432/0xc70 <4> [<ffffffff8143d38e>] __kfree_skb+0x1e/0xa0 <4> [<ffffffff81496dd4>] tcp_ack+0x3b4/0x12c0 <4> [<ffffffffa01810d5>] ? ipt_do_table+0x295/0x678 [ip_tables] The trap seems consistent across several (although always CentOS) Kernel revisions including 2.6.32.431.3.1 shipped with 6.5 and manifests in the same way with the following combinations.. 1. 2.6.32.385 Kernels from 6.4 and Open VM tools RPM from VMWare package feed. 2. 2.6.32.385 Kernels from 6.4 with Open VM Tools with modules built for the Kernel. 3. 2.6.32.431.3.1 Kernel from 6.5 using vmxnet3 drivers included in the Kernel. Tracing skb_set_owner I isolated the failing operation to an inline function in sock.h which seems to be present in current Linux 3.x Kernels also. static inline int sk_has_account(struct sock *sk) { /* return true if protocol supports memory accounting */ return !!sk->sk_prot->memory_allocated; } The faulting instruction actually being the bottom one here.. /usr/src/debug/kernel-2.6.32-358.11.1.el6/linux-2.6.32-358.11.1.el6.x86_64/include/net/sock.h: 970 0xffffffff8148fd58 <skb_set_owner_r+72>: mov 0x30(%r12),%rax /usr/src/debug/kernel-2.6.32-358.11.1.el6/linux-2.6.32-358.11.1.el6.x86_64/include/net/sock.h: 1515 0xffffffff8148fd5d <skb_set_owner_r+77>: mov 0xe0(%rbx),%edx /usr/src/debug/kernel-2.6.32-358.11.1.el6/linux-2.6.32-358.11.1.el6.x86_64/include/net/sock.h: 1007 0xffffffff8148fd63 <skb_set_owner_r+83>: cmpq $0x0,0xb0(%rax) And dumping the particular sock structure reveals the problem to be that the sk->sk_prot pointer (actually that's a define pointing to __sk_common.skc_prot) to be NULL. crash> *sock 0xffff8800a405f7B0 struct sock { __sk_common = { { skc_node = { next = 0x0, pprev = 0x0 }, skc_nulls_node = { next = 0x0, pprev = 0x0 } }, skc_refcnt = { counter = 0 }, skc_hash = 0, skc_family = 0, skc_state = 0 '\000', skc_reuse = 0 '\000', skc_bound_dev_if = 0, skc_bind_node = { next = 0xcd498725cd498171, pprev = 0x1803f8a043 }, skc_prot = 0x0, skc_net = 0x5b4000005b4 }, I'm somewhat baffled as to how a structure like this can occur since the socket when constructed, either for listening or for connecting, should have skc_prot pointed to an appropriate handler and this would seem to obviate the need to additionally protect the check in sk_has_account by checking the skc_prot pointer first. I was wondering if anybody has seen anything similar or can suggest how a sock can end up in a state without skc_prot populated. Regards, Andy

1 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

devel February 2014