public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Daniel Borkmann <dborkman@redhat.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Andrew Morton <akpm@linux-foundation.org>,
	linux-next@vger.kernel.org, linux-kernel@vger.kernel.org,
	David Miller <davem@davemloft.net>,
	netdev@vger.kernel.org, Nicolas Schichan <nschichan@freebox.fr>
Subject: Re: linux-next: manual merge of the akpm tree with the net-next tree
Date: Wed, 22 May 2013 11:20:51 +0200	[thread overview]
Message-ID: <519C8DF3.7000605@redhat.com> (raw)
In-Reply-To: <20130522095436.66e63c613c41da01cd103208@canb.auug.org.au>

[-- Attachment #1: Type: text/plain, Size: 501 bytes --]

On 05/22/2013 01:54 AM, Stephen Rothwell wrote:
> Hi Daniel,
>
> On Tue, 21 May 2013 09:44:13 +0200 Daniel Borkmann <dborkman@redhat.com> wrote:
>>
>> Also seccomp_jit_free() needs a change otherwise the kernel won't build
>> with CONFIG_SECCOMP_FILTER_JIT enabled since the work_struct is initialized
>> with the bpf_jit_free_worker() callback, which is no longer existent.
>>
>> Do you want me to send you a patch?
>
> Yes, please.

In case this is still needed, patch attached. That should fix it.

[-- Attachment #2: 0001-arm-bpf_jit-fixup-build-error-in-seccomp_jit_free.patch --]
[-- Type: text/x-patch, Size: 1395 bytes --]

>From 72d68685f31b84f64826740cf3d33ba6d8d28ffc Mon Sep 17 00:00:00 2001
Message-Id: <72d68685f31b84f64826740cf3d33ba6d8d28ffc.1369214198.git.dborkman@redhat.com>
In-Reply-To: <cover.1369214198.git.dborkman@redhat.com>
References: <cover.1369214198.git.dborkman@redhat.com>
From: Daniel Borkmann <dborkman@redhat.com>
Date: Wed, 22 May 2013 11:12:31 +0200
Subject: [PATCH] arm: bpf_jit: fixup build error in seccomp_jit_free

bpf_jit_free_worker() no longer exist, so get seccomp_jit_free()
in line with bpf_jit_free().

Signed-off-by: Daniel Borkmann <dborkman@redhat.com>
---
 arch/arm/net/bpf_jit_32.c | 13 ++-----------
 1 file changed, 2 insertions(+), 11 deletions(-)

diff --git a/arch/arm/net/bpf_jit_32.c b/arch/arm/net/bpf_jit_32.c
index 62aca35..3fe001d 100644
--- a/arch/arm/net/bpf_jit_32.c
+++ b/arch/arm/net/bpf_jit_32.c
@@ -969,18 +969,9 @@ void seccomp_jit_compile(struct seccomp_filter *fp)
 
 void seccomp_jit_free(struct seccomp_filter *fp)
 {
-	struct work_struct *work;
 	void *bpf_func = seccomp_filter_get_bpf_func(fp);
 
-	if (bpf_func != sk_run_filter) {
-		/*
-		 * seccomp_jit_free() can be called from softirq; module_free()
-		 * requires process context.
-		 */
-		work = (struct work_struct *)bpf_func;
-
-		INIT_WORK(work, bpf_jit_free_worker);
-		schedule_work(work);
-	}
+	if (bpf_func != sk_run_filter)
+		module_free(NULL, bpf_func);
 }
 #endif
-- 
1.7.11.7


  reply	other threads:[~2013-05-22  9:21 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-21  4:25 linux-next: manual merge of the akpm tree with the net-next tree Stephen Rothwell
2013-05-21  7:44 ` Daniel Borkmann
2013-05-21 23:54   ` Stephen Rothwell
2013-05-22  9:20     ` Daniel Borkmann [this message]
  -- strict thread matches above, loose matches on Subject: below --
2020-06-02  9:30 Stephen Rothwell
2020-06-02  9:45 ` Stephen Rothwell
2019-07-03 10:49 Stephen Rothwell
2018-01-16  4:51 Stephen Rothwell
2017-03-20  5:10 Stephen Rothwell
2017-02-07  5:23 Stephen Rothwell
2017-02-07  8:40 ` Marc Kleine-Budde
2017-02-07  9:45   ` Stephen Rothwell
2015-05-14  7:39 Stephen Rothwell
2015-05-14  7:38 Stephen Rothwell
2014-07-23  8:18 Stephen Rothwell
2013-11-06  9:00 Stephen Rothwell
2013-11-06  8:55 Stephen Rothwell
2013-05-21  4:32 Stephen Rothwell
2013-05-21  4:29 Stephen Rothwell
2013-05-21 20:04 ` Andrew Morton
2013-05-22  7:07   ` David Miller
2013-05-22  7:14     ` Andrew Morton
2013-05-22  7:19       ` David Miller
2013-05-22  7:48         ` Daniel Borkmann
2013-05-20  4:14 Stephen Rothwell
2013-05-20  4:11 Stephen Rothwell
2013-02-20  6:02 Stephen Rothwell
2013-02-20  6:43 ` Cong Wang
2013-02-15  6:56 Stephen Rothwell
2012-06-08  3:56 Stephen Rothwell
2011-11-23  3:27 Stephen Rothwell
2011-11-23  3:40 ` Neil Horman

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=519C8DF3.7000605@redhat.com \
    --to=dborkman@redhat.com \
    --cc=akpm@linux-foundation.org \
    --cc=davem@davemloft.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=nschichan@freebox.fr \
    --cc=sfr@canb.auug.org.au \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox