>On 12/15/2017 08:56 AM, Stephen Smalley wrote:
>> On Fri, 2017-12-15 at 03:09 +, yangjihong wrote:
>>> On 12/15/2017 10:31 PM, yangjihong wrote:
On 12/14/2017 12:42 PM, Casey Schaufler wrote:
> On 12/14/2017 9:15 AM, Stephen Smalley wrote:
>> On Thu, 2017-12-14 at 09:00 -0800,
On 12/15/2017 08:56 AM, Stephen Smalley wrote:
On Fri, 2017-12-15 at 03:09 +, yangjihong wrote:
On 12/15/2017 10:31 PM, yangjihong wrote:
On 12/14/2017 12:42 PM, Casey Schaufler wrote:
On 12/14/2017 9:15 AM, Stephen Smalley wrote:
On Thu, 2017-12-14 at 09:00 -0800, Casey Schaufler wrote:
On Fri, 2017-12-15 at 03:09 +, yangjihong wrote:
> On 12/15/2017 10:31 PM, yangjihong wrote:
> > On 12/14/2017 12:42 PM, Casey Schaufler wrote:
> > > On 12/14/2017 9:15 AM, Stephen Smalley wrote:
> > > > On Thu, 2017-12-14 at 09:00 -0800, Casey Schaufler wrote:
> > > > > On 12/14/2017 8:42 AM,
On 12/15/2017 10:31 PM, yangjihong wrote:
>On 12/14/2017 12:42 PM, Casey Schaufler wrote:
>> On 12/14/2017 9:15 AM, Stephen Smalley wrote:
>>> On Thu, 2017-12-14 at 09:00 -0800, Casey Schaufler wrote:
On 12/14/2017 8:42 AM, Stephen Smalley wrote:
> On Thu, 2017-12-14 at 08:18 -0800, Casey
On 12/14/2017 12:42 PM, Casey Schaufler wrote:
On 12/14/2017 9:15 AM, Stephen Smalley wrote:
On Thu, 2017-12-14 at 09:00 -0800, Casey Schaufler wrote:
On 12/14/2017 8:42 AM, Stephen Smalley wrote:
On Thu, 2017-12-14 at 08:18 -0800, Casey Schaufler wrote:
On 12/13/2017 7:18 AM, Stephen
On 12/14/2017 9:15 AM, Stephen Smalley wrote:
> On Thu, 2017-12-14 at 09:00 -0800, Casey Schaufler wrote:
>> On 12/14/2017 8:42 AM, Stephen Smalley wrote:
>>> On Thu, 2017-12-14 at 08:18 -0800, Casey Schaufler wrote:
On 12/13/2017 7:18 AM, Stephen Smalley wrote:
> On Wed, 2017-12-13 at
On Thu, 2017-12-14 at 09:00 -0800, Casey Schaufler wrote:
> On 12/14/2017 8:42 AM, Stephen Smalley wrote:
> > On Thu, 2017-12-14 at 08:18 -0800, Casey Schaufler wrote:
> > > On 12/13/2017 7:18 AM, Stephen Smalley wrote:
> > > > On Wed, 2017-12-13 at 09:25 +, yangjihong wrote:
> > > > > Hello,
On 12/14/2017 8:42 AM, Stephen Smalley wrote:
> On Thu, 2017-12-14 at 08:18 -0800, Casey Schaufler wrote:
>> On 12/13/2017 7:18 AM, Stephen Smalley wrote:
>>> On Wed, 2017-12-13 at 09:25 +, yangjihong wrote:
Hello,
I am doing stressing testing on 3.10 kernel(centos 7.4), to
On Thu, 2017-12-14 at 08:18 -0800, Casey Schaufler wrote:
> On 12/13/2017 7:18 AM, Stephen Smalley wrote:
> > On Wed, 2017-12-13 at 09:25 +, yangjihong wrote:
> > > Hello,
> > >
> > > I am doing stressing testing on 3.10 kernel(centos 7.4), to
> > > constantly starting numbers of docker
On 12/13/2017 7:18 AM, Stephen Smalley wrote:
> On Wed, 2017-12-13 at 09:25 +, yangjihong wrote:
>> Hello,
>>
>> I am doing stressing testing on 3.10 kernel(centos 7.4), to
>> constantly starting numbers of docker ontainers with selinux enabled,
>> and after about 2 days, the kernel
On Thu, 2017-12-14 at 03:19 +, yangjihong wrote:
> Hello,
>
> > So, does docker just keep allocating a unique category set for
> > every new container, never reusing them even if the container is
> > destroyed?
> > That would be a bug in docker IMHO. Or are you creating an
> > unbounded
Hello,
> So, does docker just keep allocating a unique category set for every new
> container, never reusing them even if the container is destroyed?
> That would be a bug in docker IMHO. Or are you creating an unbounded number
> of containers and never destroying the older ones?
I creat a
On Wed, 2017-12-13 at 09:25 +, yangjihong wrote:
> Hello,
>
> I am doing stressing testing on 3.10 kernel(centos 7.4), to
> constantly starting numbers of docker ontainers with selinux enabled,
> and after about 2 days, the kernel softlockup panic:
> [] sched_show_task+0xb8/0x120
> []
Hello,
I am doing stressing testing on 3.10 kernel(centos 7.4), to constantly starting
numbers of docker ontainers with selinux enabled, and after about 2 days, the
kernel softlockup panic:
[] sched_show_task+0xb8/0x120
[] show_lock_info+0x20f/0x3a0
[] watchdog_timer_fn+0x1da/0x2f0
[] ?
14 matches
Mail list logo