All of lore.kernel.org
 help / color / mirror / Atom feed
From: Cong Wang <xiyou.wangcong@gmail.com>
To: Paul Moore <paul@paul-moore.com>
Cc: Stephen Smalley <sds@tycho.nsa.gov>,
	Linux Kernel Network Developers <netdev@vger.kernel.org>,
	Elad Raz <e@eladraz.com>, Richard Guy Briggs <rgb@redhat.com>
Subject: Re: [Patch net] net: saving irq context for peernet2id()
Date: Thu, 20 Oct 2016 21:47:42 -0700	[thread overview]
Message-ID: <CAM_iQpUHoJP6b+qj6CEq7TjXWKuhZpAVGv-MuXGx9D7fUNGTxw@mail.gmail.com> (raw)
In-Reply-To: <CAM_iQpVFWzUm2BJZUs+-LWpKA8kubuKhzyE01_V69TEsrFnm-Q@mail.gmail.com>

On Thu, Oct 20, 2016 at 4:35 PM, Cong Wang <xiyou.wangcong@gmail.com> wrote:
> Since you want to test SELinux anyway, please test the attached one.
>

Finally my kernel config is friendly to SELinux, and now there are several
tests fails:


Test Summary Report
-------------------
sysctl/test           (Wstat: 0 Tests: 4 Failed: 2)
  Failed tests:  1-2
mmap/test             (Wstat: 0 Tests: 44 Failed: 2)
  Failed tests:  20, 26
overlay/test          (Wstat: 65280 Tests: 0 Failed: 0)
  Non-zero exit status: 255
  Parse errors: Bad plan.  You planned 121 tests but ran 0.
Files=44, Tests=306, 47 wallclock secs ( 0.23 usr  0.30 sys +  1.00
cusr  7.35 csys =  8.88 CPU)
Result: FAIL

Seems not related to my patch?

And, there is a kernel warning which is totally unrelated to my code:


[  136.788836] ------------[ cut here ]------------
[  136.793046] WARNING: CPU: 1 PID: 1345 at fs/locks.c:615
locks_unlink_lock_ctx+0xc7/0xcc
[  136.799829] CPU: 1 PID: 1345 Comm: test_lease Not tainted 4.8.0+ #271
[  136.803814] Hardware name: Bochs Bochs, BIOS Bochs 01/01/2011
[  136.803814]  ffffc900036bfd38 ffffffff8152c08e 0000000000000000
0000000000000000
[  136.803814]  ffffc900036bfd78 ffffffff810841c0 00000267036bfc88
ffff8800db2371e8
[  136.803814]  ffff8800db26f4c0 ffffc900036bfe00 ffffc900036bfe00
ffff8800db239240
[  136.803814] Call Trace:
[  136.803814]  [<ffffffff8152c08e>] dump_stack+0x67/0x90
[  136.803814]  [<ffffffff810841c0>] __warn+0xbd/0xd8
[  136.803814]  [<ffffffff81084297>] warn_slowpath_null+0x1d/0x1f
[  136.803814]  [<ffffffff8121b9cb>] locks_unlink_lock_ctx+0xc7/0xcc
[  136.803814]  [<ffffffff8121bd9e>] locks_delete_lock_ctx+0x17/0x3a
[  136.803814]  [<ffffffff8121be71>] lease_modify+0xb0/0xb9
[  136.803814]  [<ffffffff8121e868>] locks_remove_file+0x93/0xbd
[  136.803814]  [<ffffffff811d903d>] __fput+0xd0/0x19b
[  136.803814]  [<ffffffff811d913e>] ____fput+0xe/0x10
[  136.803814]  [<ffffffff8109ff86>] task_work_run+0x6c/0x97
[  136.803814]  [<ffffffff8100188a>] prepare_exit_to_usermode+0xb0/0xcc
[  136.803814]  [<ffffffff81001a04>] syscall_return_slowpath+0x15e/0x1c2
[  136.803814]  [<ffffffff81001ad7>] do_syscall_64+0x6f/0x76
[  136.803814]  [<ffffffff81b22424>] entry_SYSCALL64_slow_path+0x25/0x25
[  138.538370] ---[ end trace 90914a16bd3272b8 ]---

  reply	other threads:[~2016-10-21  4:48 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-10-20  6:52 [Patch net] net: saving irq context for peernet2id() Cong Wang
2016-10-20 10:17 ` Nicolas Dichtel
2016-10-20 17:17   ` Cong Wang
2016-10-20 14:58 ` Stephen Smalley
2016-10-20 18:29   ` Cong Wang
2016-10-20 19:04     ` Cong Wang
2016-10-20 19:07     ` Paul Moore
2016-10-20 23:35       ` Cong Wang
2016-10-21  4:47         ` Cong Wang [this message]
2016-10-21 13:51           ` Stephen Smalley
2016-10-21 16:19         ` Paul Moore
2016-10-21 18:02           ` Cong Wang
2016-10-21 19:39             ` Richard Guy Briggs
2016-10-21 20:15               ` Paul Moore
2016-10-21 20:33                 ` David Miller
2016-10-21 20:53                   ` Paul Moore
2016-10-22  1:55                     ` Paul Moore
2016-10-22  3:34                       ` Cong Wang
2016-10-22  3:53                   ` Cong Wang
2016-10-21 20:03             ` Paul Moore
2016-10-22  3:26               ` Cong Wang
2016-10-22 19:02                 ` Paul Moore

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CAM_iQpUHoJP6b+qj6CEq7TjXWKuhZpAVGv-MuXGx9D7fUNGTxw@mail.gmail.com \
    --to=xiyou.wangcong@gmail.com \
    --cc=e@eladraz.com \
    --cc=netdev@vger.kernel.org \
    --cc=paul@paul-moore.com \
    --cc=rgb@redhat.com \
    --cc=sds@tycho.nsa.gov \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.