From: Vlad Yasevich <vladislav.yasevich@hp.com>
To: David Miller <davem@davemloft.net>
Cc: netdev@vger.kernel.org, linux-sctp@vger.kernel.org
Subject: Re: [PATC] sctp: various fixes
Date: Mon, 21 Jul 2008 15:19:34 +0000 [thread overview]
Message-ID: <4884A906.1000602@hp.com> (raw)
In-Reply-To: <20080721.080535.194149976.davem@davemloft.net>
David Miller wrote:
> From: Vlad Yasevich <vladislav.yasevich@hp.com>
> Date: Mon, 21 Jul 2008 09:12:21 -0400
>
>> David Miller wrote:
>>> From: David Miller <davem@davemloft.net>
>>> Date: Fri, 18 Jul 2008 23:08:33 -0700 (PDT)
>>>
>>>> From: Vlad Yasevich <vladislav.yasevich@hp.com>
>>>> Date: Sat, 19 Jul 2008 00:26:45 -0400
>>>>
>>>>> This is a bunch of SCTP fixes that have accumlated over the past week or
>>>>> so.
>>>> All applied, thanks Vlad.
>>> Vlad, I had to add the following fix to the tree in order
>>> to unbreak the build when CONFIG_HIGHMEM is enabled.
>>>
>> ahh... since tcp isn't a module, it didn't trigger that.
>>
>> Thanks Dave. I didn't think about turning highmem off..
>
> No problem, but the problematic case was turning highmem on :-)
>
argh.....
CONFIG_HIGHMEM=y
...
CONFIG_SCTP=y
Ran my tests in kvm and it's easier to build stuff in.
-vlad
WARNING: multiple messages have this Message-ID (diff)
From: Vlad Yasevich <vladislav.yasevich@hp.com>
To: David Miller <davem@davemloft.net>
Cc: netdev@vger.kernel.org, linux-sctp@vger.kernel.org
Subject: Re: [PATC] sctp: various fixes
Date: Mon, 21 Jul 2008 11:19:34 -0400 [thread overview]
Message-ID: <4884A906.1000602@hp.com> (raw)
In-Reply-To: <20080721.080535.194149976.davem@davemloft.net>
David Miller wrote:
> From: Vlad Yasevich <vladislav.yasevich@hp.com>
> Date: Mon, 21 Jul 2008 09:12:21 -0400
>
>> David Miller wrote:
>>> From: David Miller <davem@davemloft.net>
>>> Date: Fri, 18 Jul 2008 23:08:33 -0700 (PDT)
>>>
>>>> From: Vlad Yasevich <vladislav.yasevich@hp.com>
>>>> Date: Sat, 19 Jul 2008 00:26:45 -0400
>>>>
>>>>> This is a bunch of SCTP fixes that have accumlated over the past week or
>>>>> so.
>>>> All applied, thanks Vlad.
>>> Vlad, I had to add the following fix to the tree in order
>>> to unbreak the build when CONFIG_HIGHMEM is enabled.
>>>
>> ahh... since tcp isn't a module, it didn't trigger that.
>>
>> Thanks Dave. I didn't think about turning highmem off..
>
> No problem, but the problematic case was turning highmem on :-)
>
argh.....
CONFIG_HIGHMEM=y
...
CONFIG_SCTP=y
Ran my tests in kvm and it's easier to build stuff in.
-vlad
next prev parent reply other threads:[~2008-07-21 15:19 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-19 4:26 [PATC] sctp: various fixes Vlad Yasevich
2008-07-19 4:26 ` Vlad Yasevich
2008-07-19 4:26 ` [PATCH 1/7] sctp: Don't abort initialization when CONFIG_PROC_FS=n Vlad Yasevich
2008-07-19 4:26 ` Vlad Yasevich
2008-07-19 4:26 ` [PATCH 2/7] sctp: Prevent uninitialized memory access Vlad Yasevich
2008-07-19 4:26 ` Vlad Yasevich
2008-07-19 4:26 ` [PATCH 3/7] sctp: Support ipv6only AF_INET6 sockets Vlad Yasevich
2008-07-19 4:26 ` Vlad Yasevich
2008-07-19 4:26 ` [PATCH 4/7] sctp: Do not leak memory on multiple listen() calls Vlad Yasevich
2008-07-19 4:26 ` Vlad Yasevich
2008-07-19 4:26 ` [PATCH 5/7] sctp: Allow only 1 listening socket with SO_REUSEADDR Vlad Yasevich
2008-07-19 4:26 ` Vlad Yasevich
2008-07-19 4:26 ` [PATCH 6/7] sctp: remove unnecessary byteshifting, calculate directly in big-endian Vlad Yasevich
2008-07-19 4:26 ` Vlad Yasevich
2008-07-19 4:26 ` [PATCH 7/7] sctp: Update sctp global memory limit allocations Vlad Yasevich
2008-07-19 4:26 ` Vlad Yasevich
2008-07-19 6:08 ` [PATC] sctp: various fixes David Miller
2008-07-19 6:08 ` David Miller
2008-07-20 5:40 ` David Miller
2008-07-20 5:40 ` David Miller
2008-07-21 13:12 ` Vlad Yasevich
2008-07-21 13:12 ` Vlad Yasevich
2008-07-21 15:05 ` David Miller
2008-07-21 15:05 ` David Miller
2008-07-21 15:19 ` Vlad Yasevich [this message]
2008-07-21 15:19 ` Vlad Yasevich
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=4884A906.1000602@hp.com \
--to=vladislav.yasevich@hp.com \
--cc=davem@davemloft.net \
--cc=linux-sctp@vger.kernel.org \
--cc=netdev@vger.kernel.org \
/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.