<div class="gmail_quote">On Tue, Jun 22, 2010 at 1:52 PM, Ben Pfaff <span dir="ltr"><<a href="mailto:blp@nicira.com">blp@nicira.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<div><div></div><div class="h5">On Tue, Jun 22, 2010 at 01:37:35PM -0700, Jesse Gross wrote:<br>
> On Tue, Jun 22, 2010 at 1:29 PM, Ben Pfaff <<a href="mailto:blp@nicira.com">blp@nicira.com</a>> wrote:<br>
><br>
> > On Tue, Jun 22, 2010 at 01:14:21PM -0700, Jesse Gross wrote:<br>
> > > An "invalid module format" error message can mean that a module<br>
> > > that exports the same symbols as us is already loaded.<br>
> ><br>
> > Your patch came through when I was in the middle of writing up a similar<br>
> > patch. But mine has more details.<br>
> ><br>
> > What do you think?<br>
> ><br>
><br>
> Your version is probably more useful. One reason that I was intentionally a<br>
> little vague is that the bridge is not the only module that exports the same<br>
> symbols - this question has come up before and the problem was the OpenFlow<br>
> reference implementation's module.<br>
<br>
</div></div>Good point.<br>
<br>
Here's a revised version then. (I actually tested this against OpenFlow<br>
0.9.0, the last official release to include a kernel module, so I know<br>
that the advice is correct.)<br></blockquote><div><br></div><div>Looks good, thanks. </div></div>