From: Prarit Bhargava <prarit@redhat.com>
To: Florian Westphal <fw@strlen.de>
Cc: David Miller <davem@davemloft.net>,
fbl@redhat.com, netdev@vger.kernel.org, agospoda@redhat.com,
nhorman@redhat.com, lwoodman@redhat.com, john.haxby@oracle.com
Subject: Re: [PATCH]: Add Network Sysrq Support
Date: Wed, 22 Jun 2011 08:19:33 -0400 [thread overview]
Message-ID: <4E01DDD5.8020707@redhat.com> (raw)
In-Reply-To: <20110622105434.GE16021@Chamillionaire.breakpoint.cc>
On 06/22/2011 06:54 AM, Florian Westphal wrote:
> Prarit Bhargava <prarit@redhat.com> wrote:
>
> [ cc'd John Haxby, who worked on xt_SYSREQ ]
>
>
>> On 06/21/2011 06:58 PM, David Miller wrote:
>>
>>> From: Florian Westphal <fw@strlen.de>
>>> Date: Wed, 22 Jun 2011 00:56:45 +0200
>>>
>>>> This is one of the reasons why I still think that
>>>> xt_SYSREQ would be the better solution, you get all
>>>> kinds of filtering features for free.
>>>>
>>>> You could even use crazy things like '-m time' to restrict
>>>> sysreq availability to working hours and whatnot.
>>>>
>>>>
>>> Agreed.
>>>
>> Using the netfilter xt-SYSRQ code seems to store the entered code and
>> execute it later after the system has returned to a normal state....
>> which is much too late to be useful.
>>
> The target handler of the kernel part invokes handle_sysrq(),
> I don't see any delaying/queueing?
>
Yeah ... It just occurred to me on the way into the office that I made a
mistake.
... What if the "slow down" I'm seeing is due to the network layer? ...
but why would ping work and the xt_SYSRQ not work?
Either way ... I have a feeling that I'm on to something,
P.
next prev parent reply other threads:[~2011-06-22 12:19 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-21 13:00 [PATCH]: Add Network Sysrq Support Prarit Bhargava
2011-06-21 17:08 ` Stephen Hemminger
2011-06-21 18:30 ` Neil Horman
2011-06-21 20:09 ` Randy Dunlap
2011-06-21 20:37 ` Florian Westphal
2011-06-21 20:46 ` Randy Dunlap
2011-06-21 22:12 ` Prarit Bhargava
2011-06-21 22:05 ` Flavio Leitner
2011-06-21 22:26 ` Prarit Bhargava
2011-06-21 23:32 ` Flavio Leitner
2011-06-21 22:56 ` Florian Westphal
2011-06-21 22:58 ` David Miller
2011-06-22 10:26 ` Prarit Bhargava
2011-06-22 10:35 ` David Miller
2011-06-22 10:42 ` Prarit Bhargava
2011-06-22 10:54 ` Florian Westphal
2011-06-22 12:19 ` Prarit Bhargava [this message]
2011-06-22 12:37 ` John Haxby
2011-06-22 17:39 ` Prarit Bhargava
2011-06-22 18:46 ` John Haxby
2011-06-22 20:29 ` David Miller
2011-06-22 18:57 ` John Haxby
2011-06-22 20:27 ` David Miller
2011-06-24 14:37 ` John Haxby
2011-06-22 7:55 ` WANG Cong
2011-06-22 15:29 ` Andi Kleen
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=4E01DDD5.8020707@redhat.com \
--to=prarit@redhat.com \
--cc=agospoda@redhat.com \
--cc=davem@davemloft.net \
--cc=fbl@redhat.com \
--cc=fw@strlen.de \
--cc=john.haxby@oracle.com \
--cc=lwoodman@redhat.com \
--cc=netdev@vger.kernel.org \
--cc=nhorman@redhat.com \
/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;
as well as URLs for NNTP newsgroup(s).