<?xml version="1.0" ?>

<kc>

<title>Kernel Traffic</title>

<author contact="mailto:zbrown@tumblerings.org">Zack Brown</author>

<issue num="322" date="03 Sep 2005 00:00:00 -0800" />

<mailbox-stats>
	<global-stats>
		<generated-at>Sat Sep  3 15:54:31 2005</generated-at>
		<first-message>Tue Jul 12 00:28:12 2005</first-message>
		<last-message>Fri Aug  5 15:47:59 2005</last-message>
		<totals>
			<n-messages>2060</n-messages>
			<n-is-reply>1542</n-is-reply>
			<avg-resp-time>541:54:50</avg-resp-time>
			<n-pgp-signed>65</n-pgp-signed>
			<total-size>12MB</total-size>
			<avg-size>6KB</avg-size>
			<n-attachments>76</n-attachments>
			<att-size>875KB</att-size>
			<bussiest-day-in-n day="2005-07-29"><n-msgs>349</n-msgs><n-bytes>2MB</n-bytes></bussiest-day-in-n>
			<bussiest-day-in-bytes day="2005-07-29"><n-msgs>349</n-msgs><n-bytes>2MB</n-bytes></bussiest-day-in-bytes>
			<n-writers>679</n-writers>
			<wrote-more-then-1-message>266</wrote-more-then-1-message>
			<n-lines>192147</n-lines>
			<header-size>111262</header-size>
			<n-user-agents>65</n-user-agents>
			<n-organisations>46</n-organisations>
			<n-toplevel-domains>37</n-toplevel-domains>
			<avg-spam-score>-13.594612</avg-spam-score>
				<spammiest-writer><score>3.299000</score><name>arouna</name></spammiest-writer>
		</totals>
		<averages>
			<lines-per-message>93</lines-per-message>
			<lines-per-header>54</lines-per-header>
			<header-percent-of-message>57.90%</header-percent-of-message>
			<header-percent-of-total>44.55%</header-percent-of-total>
			<line-length>31</line-length>
		</averages>
		<importance>
			<low>0.00%</low>
			<normal>0.44%</normal>
			<high>0.00%</high>
		</importance>

	</global-stats>
	<top-writers>
		<top-writer rank="1">
			<e-mail-addr>pavel&#32;machek</e-mail-addr>
			<n-messages>81</n-messages>
			<avg-size>4KB</avg-size>
			<total-size>323KB</total-size>
			<mostly-written-at>13:50</mostly-written-at>
		</top-writer>
		<top-writer rank="2">
			<e-mail-addr>akpm@osdl.org</e-mail-addr>
			<n-messages>78</n-messages>
			<avg-size>5KB</avg-size>
			<total-size>359KB</total-size>
			<mostly-written-at>13:41</mostly-written-at>
		</top-writer>
		<top-writer rank="3">
			<e-mail-addr>ingo&#32;molnar</e-mail-addr>
			<n-messages>61</n-messages>
			<avg-size>6KB</avg-size>
			<total-size>310KB</total-size>
			<mostly-written-at>14:25</mostly-written-at>
		</top-writer>
		<top-writer rank="4">
			<e-mail-addr>steven&#32;rostedt</e-mail-addr>
			<n-messages>56</n-messages>
			<avg-size>5KB</avg-size>
			<total-size>279KB</total-size>
			<mostly-written-at>13:53</mostly-written-at>
		</top-writer>
		<top-writer rank="5">
			<e-mail-addr>lee&#32;revell</e-mail-addr>
			<n-messages>55</n-messages>
			<avg-size>4KB</avg-size>
			<total-size>169KB</total-size>
			<mostly-written-at>14:02</mostly-written-at>
		</top-writer>
	</top-writers>
	<top-subjects>
		<top-subject rank="1">
			<subject>power&#32;consumption&#32;hz100,&#32;hz250,&#32;hz1000:&#32;new&#32;numbers</subject>
			<n-messages>78</n-messages>
			<avg-size>5KB</avg-size>
			<total-size>319KB</total-size>
			<mostly-written-at>13:20</mostly-written-at>
			<first-msg>1122693342</first-msg>
			<last-msg>1123238354</last-msg>
		</top-subject>
		<top-subject rank="2">
			<subject>[patch&#32;2.6.13-rc4]&#32;fix&#32;get_user_pages&#32;bug</subject>
			<n-messages>63</n-messages>
			<avg-size>5KB</avg-size>
			<total-size>311KB</total-size>
			<mostly-written-at>14:33</mostly-written-at>
			<first-msg>1122914547</first-msg>
			<last-msg>1123230607</last-msg>
		</top-subject>
		<top-subject rank="3">
			<subject>revert&#32;yenta&#32;free_irq&#32;on&#32;suspend</subject>
			<n-messages>58</n-messages>
			<avg-size>5KB</avg-size>
			<total-size>245KB</total-size>
			<mostly-written-at>14:07</mostly-written-at>
			<first-msg>1122759282</first-msg>
			<last-msg>1123105332</last-msg>
		</top-subject>
		<top-subject rank="4">
			<subject>[patch]&#32;real-time&#32;preemption,&#32;-rt-2.6.13-rc4-v0.7.52-01</subject>
			<n-messages>45</n-messages>
			<avg-size>5KB</avg-size>
			<total-size>217KB</total-size>
			<mostly-written-at>15:27</mostly-written-at>
			<first-msg>1122775425</first-msg>
			<last-msg>1123194050</last-msg>
		</top-subject>
		<top-subject rank="5">
			<subject>[2.6&#32;patch]&#32;schedule&#32;obsolete&#32;oss&#32;drivers&#32;for&#32;removal</subject>
			<n-messages>35</n-messages>
			<avg-size>4KB</avg-size>
			<total-size>135KB</total-size>
			<mostly-written-at>15:58</mostly-written-at>
			<first-msg>1122398827</first-msg>
			<last-msg>1122874614</last-msg>
		</top-subject>
	</top-subjects>
	<top-receivers>
		<top-receiver rank="1">
			<e-mail-addr>linux-kernel@vger.kernel.org</e-mail-addr>
			<n-messages>339</n-messages>
			<avg-size>8KB</avg-size>
			<total-size>3MB</total-size>
			<mostly-written-at>14:10</mostly-written-at>
		</top-receiver>
		<top-receiver rank="2">
			<e-mail-addr>akpm@osdl.org</e-mail-addr>
			<n-messages>266</n-messages>
			<avg-size>7KB</avg-size>
			<total-size>2MB</total-size>
			<mostly-written-at>13:29</mostly-written-at>
		</top-receiver>
		<top-receiver rank="3">
			<e-mail-addr>linus&#32;torvalds</e-mail-addr>
			<n-messages>110</n-messages>
			<avg-size>7KB</avg-size>
			<total-size>661KB</total-size>
			<mostly-written-at>13:44</mostly-written-at>
		</top-receiver>
		<top-receiver rank="4">
			<e-mail-addr>pavel&#32;machek</e-mail-addr>
			<n-messages>77</n-messages>
			<avg-size>5KB</avg-size>
			<total-size>326KB</total-size>
			<mostly-written-at>14:04</mostly-written-at>
		</top-receiver>
		<top-receiver rank="5">
			<e-mail-addr>ingo&#32;molnar</e-mail-addr>
			<n-messages>64</n-messages>
			<avg-size>5KB</avg-size>
			<total-size>304KB</total-size>
			<mostly-written-at>13:20</mostly-written-at>
		</top-receiver>
	</top-receivers>
	<top-ccers>
		<top-ccers rank="1">
			<e-mail-addr>linux-kernel@vger.kernel.org</e-mail-addr>
			<n-messages>929</n-messages>
			<avg-size>6KB</avg-size>
			<total-size>5MB</total-size>
			<mostly-written-at>13:50</mostly-written-at>
		</top-ccers>
		<top-ccers rank="2">
			<e-mail-addr>akpm@osdl.org</e-mail-addr>
			<n-messages>262</n-messages>
			<avg-size>5KB</avg-size>
			<total-size>2MB</total-size>
			<mostly-written-at>13:59</mostly-written-at>
		</top-ccers>
		<top-ccers rank="3">
			<e-mail-addr>torvalds@osdl.org</e-mail-addr>
			<n-messages>71</n-messages>
			<avg-size>5KB</avg-size>
			<total-size>324KB</total-size>
			<mostly-written-at>14:21</mostly-written-at>
		</top-ccers>
		<top-ccers rank="4">
			<e-mail-addr>ingo&#32;molnar</e-mail-addr>
			<n-messages>66</n-messages>
			<avg-size>6KB</avg-size>
			<total-size>366KB</total-size>
			<mostly-written-at>15:07</mostly-written-at>
		</top-ccers>
		<top-ccers rank="5">
			<e-mail-addr>pavel&#32;machek</e-mail-addr>
			<n-messages>49</n-messages>
			<avg-size>5KB</avg-size>
			<total-size>199KB</total-size>
			<mostly-written-at>13:53</mostly-written-at>
		</top-ccers>
	</top-ccers>
	<top-level-domains>
		<tld rank="1">
			<name>com</name>
			<freq>767</freq>
			<avg-size>7KB</avg-size>
			<total-size>5MB</total-size>
		</tld>
		<tld rank="2">
			<name>org</name>
			<freq>369</freq>
			<avg-size>6KB</avg-size>
			<total-size>2MB</total-size>
		</tld>
		<tld rank="3">
			<name>de</name>
			<freq>213</freq>
			<avg-size>6KB</avg-size>
			<total-size>2MB</total-size>
		</tld>
		<tld rank="4">
			<name>net</name>
			<freq>162</freq>
			<avg-size>7KB</avg-size>
			<total-size>976KB</total-size>
		</tld>
		<tld rank="5">
			<name>cz</name>
			<freq>114</freq>
			<avg-size>5KB</avg-size>
			<total-size>477KB</total-size>
		</tld>
	</top-level-domains>
	<top-timezones>
		<tz rank="1">
			<name>+0200</name>
			<freq>680</freq>
			<avg-size>6KB</avg-size>
			<total-size>4MB</total-size>
		</tz>
		<tz rank="2">
			<name>-0700</name>
			<freq>453</freq>
			<avg-size>6KB</avg-size>
			<total-size>3MB</total-size>
		</tz>
		<tz rank="3">
			<name>-0400</name>
			<freq>366</freq>
			<avg-size>6KB</avg-size>
			<total-size>3MB</total-size>
		</tz>
		<tz rank="4">
			<name>+0100</name>
			<freq>150</freq>
			<avg-size>5KB</avg-size>
			<total-size>658KB</total-size>
		</tz>
		<tz rank="5">
			<name>+1000</name>
			<freq>107</freq>
			<avg-size>6KB</avg-size>
			<total-size>575KB</total-size>
		</tz>
	</top-timezones>
	<top-organisations>
		<org rank="1">
			<name>kihon&#32;technologies</name>
			<freq>56</freq>
			<bytes>279KB</bytes>
		</org>
		<org rank="2">
			<name>www.scatter.mine.nu</name>
			<freq>10</freq>
			<bytes>35KB</bytes>
		</org>
		<org rank="3">
			<name>montavista&#32;software</name>
			<freq>9</freq>
			<bytes>40KB</bytes>
		</org>
		<org rank="4">
			<name>none,&#32;usuallly&#32;detectable&#32;by&#32;casual&#32;observers</name>
			<freq>7</freq>
			<bytes>28KB</bytes>
		</org>
		<org rank="5">
			<name>ibm</name>
			<freq>5</freq>
			<bytes>43KB</bytes>
		</org>
	</top-organisations>
	<top-user-agents>
		<useragent rank="1">
			<name>mozilla</name>
			<freq>57</freq>
			<bytes>2MB</bytes>
		</useragent>
		<useragent rank="2">
			<name>evolution</name>
			<freq>43</freq>
			<bytes>2MB</bytes>
		</useragent>
		<useragent rank="3">
			<name>mutt/1.5.9i</name>
			<freq>34</freq>
			<bytes>2MB</bytes>
		</useragent>
		<useragent rank="4">
			<name>mozilla/5.0</name>
			<freq>24</freq>
			<bytes>750KB</bytes>
		</useragent>
		<useragent rank="5">
			<name>mutt/1.4.2.1i</name>
			<freq>14</freq>
			<bytes>515KB</bytes>
		</useragent>
	</top-user-agents>
	<messages-per-day>
		<Sunday><msgs>207</msgs><bytes>2MB</bytes></Sunday>
		<Monday><msgs>315</msgs><bytes>2MB</bytes></Monday>
		<Tuesday><msgs>299</msgs><bytes>2MB</bytes></Tuesday>
		<Wednesday><msgs>307</msgs><bytes>2MB</bytes></Wednesday>
		<Thursday><msgs>308</msgs><bytes>2MB</bytes></Thursday>
		<Friday><msgs>397</msgs><bytes>3MB</bytes></Friday>
		<Saturday><msgs>217</msgs><bytes>2MB</bytes></Saturday>
	</messages-per-day>
	<messages-per-month>
		<Jan><msgs>0</msgs><bytes>0</bytes></Jan>
		<Feb><msgs>0</msgs><bytes>0</bytes></Feb>
		<Mar><msgs>0</msgs><bytes>0</bytes></Mar>
		<Apr><msgs>0</msgs><bytes>0</bytes></Apr>
		<May><msgs>0</msgs><bytes>0</bytes></May>
		<Jun><msgs>0</msgs><bytes>0</bytes></Jun>
		<Jul><msgs>1142</msgs><bytes>7MB</bytes></Jul>
		<Aug><msgs>908</msgs><bytes>5MB</bytes></Aug>
		<Sep><msgs>0</msgs><bytes>0</bytes></Sep>
		<Oct><msgs>0</msgs><bytes>0</bytes></Oct>
		<Nov><msgs>0</msgs><bytes>0</bytes></Nov>
		<Dec><msgs>0</msgs><bytes>0</bytes></Dec>
	</messages-per-month>
	<messages-per-day-of-month>
		<day-1><msgs>274</msgs><bytes>2MB</bytes></day-1>
		<day-2><msgs>242</msgs><bytes>2MB</bytes></day-2>
		<day-3><msgs>204</msgs><bytes>2MB</bytes></day-3>
		<day-4><msgs>158</msgs><bytes>922KB</bytes></day-4>
		<day-5><msgs>30</msgs><bytes>124KB</bytes></day-5>
		<day-6><msgs>0</msgs><bytes>0</bytes></day-6>
		<day-7><msgs>0</msgs><bytes>0</bytes></day-7>
		<day-8><msgs>0</msgs><bytes>0</bytes></day-8>
		<day-9><msgs>0</msgs><bytes>0</bytes></day-9>
		<day-10><msgs>0</msgs><bytes>0</bytes></day-10>
		<day-11><msgs>1</msgs><bytes>4KB</bytes></day-11>
		<day-12><msgs>1</msgs><bytes>12KB</bytes></day-12>
		<day-13><msgs>0</msgs><bytes>0</bytes></day-13>
		<day-14><msgs>0</msgs><bytes>0</bytes></day-14>
		<day-15><msgs>0</msgs><bytes>0</bytes></day-15>
		<day-16><msgs>0</msgs><bytes>0</bytes></day-16>
		<day-17><msgs>0</msgs><bytes>0</bytes></day-17>
		<day-18><msgs>2</msgs><bytes>7KB</bytes></day-18>
		<day-19><msgs>0</msgs><bytes>0</bytes></day-19>
		<day-20><msgs>0</msgs><bytes>0</bytes></day-20>
		<day-21><msgs>1</msgs><bytes>31KB</bytes></day-21>
		<day-22><msgs>18</msgs><bytes>77KB</bytes></day-22>
		<day-23><msgs>14</msgs><bytes>152KB</bytes></day-23>
		<day-24><msgs>14</msgs><bytes>53KB</bytes></day-24>
		<day-25><msgs>38</msgs><bytes>334KB</bytes></day-25>
		<day-26><msgs>56</msgs><bytes>252KB</bytes></day-26>
		<day-27><msgs>103</msgs><bytes>520KB</bytes></day-27>
		<day-28><msgs>149</msgs><bytes>808KB</bytes></day-28>
		<day-29><msgs>349</msgs><bytes>2MB</bytes></day-29>
		<day-30><msgs>203</msgs><bytes>1016KB</bytes></day-30>
		<day-31><msgs>193</msgs><bytes>2MB</bytes></day-31>
	</messages-per-day-of-month>
	<messages-per-hour>
		<hour-1><msgs>47</msgs><bytes>212KB</bytes></hour-1>
		<hour-2><msgs>34</msgs><bytes>193KB</bytes></hour-2>
		<hour-3><msgs>14</msgs><bytes>86KB</bytes></hour-3>
		<hour-4><msgs>9</msgs><bytes>34KB</bytes></hour-4>
		<hour-5><msgs>4</msgs><bytes>70KB</bytes></hour-5>
		<hour-6><msgs>12</msgs><bytes>95KB</bytes></hour-6>
		<hour-7><msgs>28</msgs><bytes>145KB</bytes></hour-7>
		<hour-8><msgs>81</msgs><bytes>334KB</bytes></hour-8>
		<hour-9><msgs>112</msgs><bytes>501KB</bytes></hour-9>
		<hour-10><msgs>143</msgs><bytes>712KB</bytes></hour-10>
		<hour-11><msgs>142</msgs><bytes>800KB</bytes></hour-11>
		<hour-12><msgs>153</msgs><bytes>691KB</bytes></hour-12>
		<hour-13><msgs>141</msgs><bytes>708KB</bytes></hour-13>
		<hour-14><msgs>117</msgs><bytes>695KB</bytes></hour-14>
		<hour-15><msgs>120</msgs><bytes>756KB</bytes></hour-15>
		<hour-16><msgs>121</msgs><bytes>776KB</bytes></hour-16>
		<hour-17><msgs>148</msgs><bytes>1011KB</bytes></hour-17>
		<hour-18><msgs>94</msgs><bytes>495KB</bytes></hour-18>
		<hour-19><msgs>73</msgs><bytes>470KB</bytes></hour-19>
		<hour-20><msgs>80</msgs><bytes>545KB</bytes></hour-20>
		<hour-21><msgs>111</msgs><bytes>637KB</bytes></hour-21>
		<hour-22><msgs>92</msgs><bytes>531KB</bytes></hour-22>
		<hour-23><msgs>91</msgs><bytes>398KB</bytes></hour-23>
	</messages-per-hour>
	<urls>
		<url-1><freq>1510</freq><url>http://vger.kernel.org/majordomo-info.html</url></url-1>
		<url-2><freq>1509</freq><url>http://www.tux.org/lkml/</url></url-2>
		<url-3><freq>10</freq><url>http://www.horde.org</url></url-3>
		<url-4><freq>9</freq><url>http://monobrasil.softwarelivre.org</url></url-4>
		<url-5><freq>9</freq><url>http://enigmail.mozdev.org</url></url-5>
	</urls>
	<top-avg-resp>
		<resp-pers rank="1">
			<name>roland&#32;dreier</name>
			<avg-resp-time>00:04:10</avg-resp-time>
			<n-replies>1</n-replies>
		</resp-pers>
		<resp-pers rank="2">
			<name>mike&#32;waychison</name>
			<avg-resp-time>00:04:14</avg-resp-time>
			<n-replies>2</n-replies>
		</resp-pers>
		<resp-pers rank="3">
			<name>nash</name>
			<avg-resp-time>00:05:59</avg-resp-time>
			<n-replies>1</n-replies>
		</resp-pers>
		<resp-pers rank="4">
			<name>mark&#32;haverkamp</name>
			<avg-resp-time>00:06:17</avg-resp-time>
			<n-replies>1</n-replies>
		</resp-pers>
		<resp-pers rank="5">
			<name>lukas&#32;hejtmanek</name>
			<avg-resp-time>00:06:18</avg-resp-time>
			<n-replies>1</n-replies>
		</resp-pers>
		<resp-pers rank="6">
			<name>john&#32;pearson</name>
			<avg-resp-time>00:14:03</avg-resp-time>
			<n-replies>1</n-replies>
		</resp-pers>
	</top-avg-resp>
	<created-with><name>mboxstats</name><version>2.8</version><developer>folkert@vanheusden.com</developer><url>http://www.vanheusden.com/mboxstats/</url></created-with>
</mailbox-stats>

<section
  title="Scheduling Obsolete OSS Drivers For Removal"
  subject="[2.6 patch] schedule obsolete OSS drivers for removal"
  archive="http://groups.google.com/group/fa.linux.kernel/msg/bc6ae36d12455636?hl=en"
  posts="46"
  startdate="26 Jul 2005 07:08:37 -0800"
  enddate="02 Aug 2005 07:55:12 -0800"
>
<topic>PCI</topic>
<topic>Sound: ALSA</topic>
<topic>Sound: OSS</topic>

<mention>Lee Revell</mention>
<mention>Jeff Garzik</mention>
<mention>Thomas Sailer</mention>

<p>Adrian Bunk said, <quote who="Adrian Bunk">This patch schedules obsolete OSS
drivers (with ALSA drivers that support the same hardware) for removal.</quote>
Thomas Sailer approved of the patch, while Jeff Garzik cautioned that before
this patch was applied, it should be confirmed that the ALSA drivers really
did support the same hardware in each case. He confirmed the via82cxxx
driver himself, but said the i810_audio driver was not ready, because <quote
who="i810_audio">ALSA doesn't have all the PCI IDs (which must be verified --
you cannot just add the PCI IDs for some hardware)</quote>. Adrian confirmed
that he had tried to confirm each driver, though he admitted that he could
have missed something.</p>

<p>Elsewhere, Lee Revell asked how many obsolete OSS drivers were included
in Adrian's patch, and Adrian replied he hadn't counted them all.</p>

</section>

<section
  title="Support For Sharp Zaurus SL-5500 LCD Power Up/Down"
  subject="[patch] Support powering sharp zaurus sl-5500 LCD up and down"
  archive="http://groups.google.com/group/linux.kernel/msg/5e7e0ed2b6a51bfb?hl=en"
  posts="10"
  startdate="27 Jul 2005 01:26:13 -0800"
  enddate="01 Aug 2005 14:14:32 -0800"
>

<mention>Andrew Morton</mention>

<p>Pavel Machek said, <quote who="Pavel Machek">This adds support for
powering Zaurus's video up and down. PDA without screen is kind of useless,
so it is quite important... I'll have to figure out how to really control
the frontlight, because LCD without that is quite hard to read.</quote>
Andrew Morton asked if Pavel would maintain this code, and Pavel agreed.</p>

</section>

<section
  title="Linux 2.6.13-rc3-mm2 Released"
  subject="2.6.13-rc3-mm2"
  archive="http://groups.google.com/group/linux.kernel/msg/b4e42251fa2bfae9?hl=en"
  posts="26"
  startdate="27 Jul 2005 01:43:30 -0800"
  enddate="29 Jul 2005 20:03:52 -0800"
>
<topic>Kernel Release Announcement</topic>

<mention>Sam Ravnborg</mention>

<p>Andrew Morton announced Linux 2.6.13-rc3-mm2, saying:</p>

<quote who="Andrew Morton">

<p><a href="ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.13-rc3/2.6.13-rc3-mm2/">ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.13-rc3/2.6.13-rc3-mm2/</a></p>

<ul>

<li>Lots of fixes and updates all over the place.  There are probably over 100
  patches here which need to go into 2.6.13.</li>

<li>

<p>A reminder that -mm commit activity may be monitored by subscribing to
  the mm-commits list.  Do</p>

<p>        echo subscribe mm-commits | mail majordomo@vger.kernel.org</p>

</li>

</ul>

</quote>

<p>Sam Ravnborg asked if the mailing list were archived anywhere, and Andrew
replied, <quote who="Andrew Morton">Not to my knowledge.</quote></p>

</section>

<section
  title="Linux 2.6.13-rc4 Released"
  subject="Linux 2.6.13-rc4"
  archive="http://groups.google.com/group/linux.kernel/msg/159946f29deae0c8?hl=en"
  posts="18"
  startdate="28 Jul 2005 15:34:29 -0800"
  enddate="02 Aug 2005 08:15:37 -0800"
>
<topic>Disks: SCSI</topic>
<topic>FS: NTFS</topic>
<topic>Kernel Release Announcement</topic>
<topic>Sound: ALSA</topic>

<mention>Andrew Morton</mention>

<p>Linus Torvalds announced Linux 2.6.13-rc4, saying:</p>

<quote who="Linus Torvalds">

<p>as many of you are aware, we were talking (not enough) about the release
process at LKS this year.</p>

<p>This ain't it.</p>

<p>This is just the regular old release "process", with some LKS backlog put
in for good measure.</p>

<p>But the good news is, that I'll try the new release process after 2.6.13
is out, which is hopefully not too far away. Which means that we should
try to let people know about the fact that if they want to merge stuff,
they should do so in the first two weeks after the 2.6.13 release, and no
later (also, no earlier either, by now).</p>

<p>So if you have a favourite kernel developer, please wake him up with a
friendly kick to the head and explain this concept to him in small
easy-to-understand words, and tell him that we're in the freeze process
for 2.6.13 now, and that he should be gathering up the patches, and make
sure they get to me _after_ 2.6.13 is out, but at that point do it in a
timely manner.</p>

<p>Ok?</p>

<p>In the meantime, here's the 2.6.13-rc4 update, with a diffstat so horribly
ugly that I won't even show it (the kernel list would eat it as too big
anyway), and I'll have to go fix my code that generates it.</p>

<p>Oh, and in case you wonder, it's ugly because a cris architecture update
with long filenames that really causes git-apply to output som rather
nasty-looking diffstats ;)</p>

<p>ALSA, IB, NTFS, SCSI (qla2xxx) and the cris architecture update.</p>

</quote>

<p>Jesper Juhl said, <quote who="Jesper Juhl">For the bennefit of
those of us who were not at LKS, could someone elaborate a bit on
"the new release process" ?</quote> Andrew Morton gave a link to <a
href="http://lwn.net/Articles/144281/">a Linux Weekly News summary</a>
of the process.</p>

</section>

<section
  title="Wireless Security Lock Driver To Detect Physical Proximity"
  subject="[PATCH] Wireless Security Lock driver."
  archive="http://groups.google.com/group/linux.kernel/msg/bd0675b772c64ee3?hl=en"
  posts="19"
  startdate="30 Jul 2005 06:51:58 -0800"
  enddate="31 Jul 2005 08:14:01 -0800"
>
<topic>USB</topic>

<p>Brian Schau said:</p>

<quote who="Brian Schau">

<p>I've attached a gzipped version of my Wireless Security Lock patch
for v2.6.13-rc4.</p>

<p>A Wireless Security Lock (WSL or weasel :-) is made up of two parts.
One part is a receiver which you plug into any available USB port.
The other part is a transmitter which at fixed intervals sends
"ping packets".</p>

<p>A "ping packet" usually consists of an ID and a flag telling if the
transmitter has just been turned on.
Both devices lights up in a nice way when a "ping packet" is send/
received.</p>

<p>The whole idea of this is that when the transmitter is brought out
of range one could have a process (such as xscreensaver) lock the
display.</p>

<p>The WSL is a toy gadget.</p>

<p>For more information see:</p>

<p>        <a href="http://www.schau.com/l/wsl/index.html">http://www.schau.com/l/wsl/index.html</a></p>

<p>The WSL driver touches these files:</p>

<pre>        drivers/usb/Makefile                    (1 line)
        drivers/usb/input/Kconfig               (10 lines)
        drivers/usb/input/Makefile              (1 line)
        drivers/usb/input/hid-core.c            (2 lines)
        drivers/usb/input/wsl.c                 (224 lines)</pre>

<p>This is my first driver for Linux - feel free to harass me if I am
not following procedures or you think the driver is lame.  Better still,
educate me :-)</p>

</quote>

<p>Pavel Machek replied, <quote who="Pavel Machek">Idea is good... but
why don't you simply use bluetooth (built into many notebooks) and
bluetooth-enabled phone? Probably could be done in userspace, too
:-).</quote> Alistair John Strachan replied:</p>

<quote who="Alistair John Strachan">

<p>There's a script to this on the gentoo wiki via BlueZ.</p>

<p><a href="http://gentoo-wiki.com/TIP_Bluetooth_Proximity_Monitor">http://gentoo-wiki.com/TIP_Bluetooth_Proximity_Monitor</a></p>

<p>I personally think the problem with this approach is that most phones have
bluetooth enabled explicitly as an option, it doesn't run all the time, or
default on. Primarily this is because bluetooth can drain your phone's
battery (though, I don't know by how much, if you're not actually
transferring data over it).</p>

<p>A CR2032 cell, in a specific piece of kit, is going to last for a lot longer
than a phone battery.</p>

</quote>

<p>But Brian also replied to Pavel, saying:</p>

<quote who="Brian Schau">

<p>WSLs are already reality.  Sitecom is a producer of
these and you can get another brand from ThinkGeek.</p>

<p>Sitecom device:
<a href="http://www.sitecom.com/products_info.php?product_id=293&amp;grp_id=1">http://www.sitecom.com/products_info.php?product_id=293&amp;grp_id=1</a></p>

<p>ThinkGeek:
<a href="http://www.thinkgeek.com/gadgets/security/698d/">http://www.thinkgeek.com/gadgets/security/698d/</a></p>

<p>Why in kernel?   Well, the device is based on the Cypress Ultra
Mouse.  So with a non WSL aware kernel the events from the WSL
will be merged into the standard mouse input queue which will
make your mouse pointer move uncontrollable - it'll jump across
the screen in a couple of steps every 3 seconds or so.
Quite amusing but not very handy!
The problem is described here:</p>

<p><a href="http://www.qbik.ch/usb/devices/showdev.php?id=3095">http://www.qbik.ch/usb/devices/showdev.php?id=3095</a></p>

<p>The WSL kernel driver will translate the device packets to a
separate event queue.</p>

<p>And you're right.  The WSL driver is not a standalone thingy -
you'll some userland tools as well.  These can be gotten from:</p>

<p><a href="http://www.schau.com/l/wsl/index.html">http://www.schau.com/l/wsl/index.html</a></p>

<p>The tools contains a patch for xscreensaver (patch submitted to
maintainer) and a small WSL monitor program which will monitor
in-range/out-of-range signals and disable/enable xscreensaver
as needed.</p>

</quote>

<p>Given the existence of the hardware, Brian's work mad sense to Pavel,
and the thread petered out.</p>

</section>

<section
  title="SquashFS Not NFS-Compatible; Fix On The Way"
  subject="squashfs seems nfs-incompatible"
  archive="http://groups.google.com/group/fa.linux.kernel/msg/d4fbec0551d820dd?hl=en"
  posts="4"
  startdate="02 Aug 2005 07:15:01 -0800"
  enddate="04 Aug 2005 14:46:28 -0800"
>
<topic>FS: NFS</topic>
<topic>FS: SquashFS</topic>

<p>Jan Engelhardt said, <quote who="Jan Engelhardt">I found out that you
cannot mount an exported squash fs. The exports(5) fsid= parameter does not
help it [like it did with unionfs].</quote> Phillip Lougher replied, <quote
who="Phillip Lougher">The exports(5) man page says fsid=num is necessary for
filesystems on non-block devices - I don't know whether this includes loopback
filesystems. Have you tried exporting a Squashfs filesystem mounted on a real
block device?</quote> Jan said, <quote who="Jan Engelhardt">Loopback is a real
block device, and no, fsid= does not help it. I have talked with the unionfs
people, because it works for them. After a short flash of idea and comparison,
it turns out that squashfs is missing sb-&gt;s_export-&gt;get_parent (the only
requirement as it seems). Includes that you have sb-&gt;s_export non-null,
of course. sb-&gt;s_export can be set within fill_super().</quote> Phillip
replied, <quote who="Phillip Lougher">Ok, thanks. I'll try and get a fix
for it in the next release.</quote></p>

</section>

<section
  title="New Documentation/kprobes.txt File"
  subject="[PATCH] Add Documentation/kprobes.txt"
  archive="http://groups.google.com/group/fa.linux.kernel/msg/ea18c27cd24a6673?hl=en"
  posts="3"
  startdate="02 Aug 2005 14:20:06 -0800"
  enddate="03 Aug 2005 14:05:03 -0800"
>

<p>Jim Keniston said, <quote who="Jim Keniston">The enclosed patch creates
Documentation/kprobes.txt, a guide to using the existing Kprobes facility
for dynamic kernel instrumentation.</quote></p>

</section>

<section
  title="New Stable Review Cycle Started For 2.6.12.4"
  subject="[00/13] -stable review"
  archive="http://groups.google.com/group/linux.kernel/msg/dcae945e9c0d59e4?hl=en"
  posts="17"
  startdate="02 Aug 2005 22:44:39 -0800"
  enddate="02 Aug 2005 23:07:52 -0800"
>
<topic>Big Memory Support</topic>
<topic>Bug Tracking</topic>
<topic>Kernel Build System</topic>

<p>Chris Wright said:</p>

<quote who="Chris Wright">

<p>This is the start of the stable review cycle for the 2.6.12.4 release.
There are 13 patches in this series, all will be posted as a response to
this one.  If anyone has any issues with these being applied, please let
us know.  If anyone is a maintainer of the proper subsystem, and wants
to add a signed-off-by: line to the patch, please respond with it.</p>

<p>These patches are sent out with a number of different people on the Cc:
line.  If you wish to be a reviewer, please email stable@kernel.org to
add your name to the list.  If you want to be off the reviewer list,
also email us.</p>

<p>Responses should be made by Friday, Aug 5 07:00:00, UTC 2005.  Anything
received after that time, might be too late.</p>

</quote>

<p>The changelog entries were included at the top of each patch:</p>

<ul>

<li>

<p>[PATCH] kbuild: build TAGS problem with O=</p>

<p>  make O=/dir TAGS</p>

<p>  fails with:</p>

<p>    MAKE   TAGS<br />
  find: security/selinux/include: No such file or directory<br />
  find: include: No such file or directory<br />
  find: include/asm-i386: No such file or directory<br />
  find: include/asm-generic: No such file or directory</p>

<p>  The problem is in this line:<br />
  ifeq ($(KBUILD_OUTPUT),)</p>

<p>KBUILD_OUTPUT is not defined (ever) after make reruns itself.  This line is
used in the TAGS, tags, and cscope makes.</p>

</li>

<li>

<p>Correct handling of fc_remote_port_add() failure case.</p>

<p>Immediately return if fc_remote_port_add() fails to allocate
resources for the rport.  Original code would result in NULL
pointer dereference upon failure.</p>

</li>

<li>If bailing out because there is nothing to receive in rp_do_receive(),
tty_ldisc_deref is not called. Failure to do so increases the ref count=20
and causes release_dev() to hang since it can't get the ref count to 0.</li>

<li>

<p>malicious 32bit app can have an elf section at 0xffffe000.  During
exec of this app, we will have a memory leak as insert_vm_struct() is
not checking for return value in syscall32_setup_pages() and thus not
freeing the vma allocated for the vsyscall page.</p>

<p>Check the return value and free the vma incase of failure.</p>

</li>

<li>

<p>This is the code to load packet data into a register:</p>

<pre>                        k = fentry->k;
                        if (k &lt; 0) {
...
                        } else {
                                u32 _tmp, *p;
                                p = skb_header_pointer(skb, k, 4, &amp;_tmp);
                                if (p != NULL) {
                                        A = ntohl(*p);
                                        continue;
                                }
                        }</pre>

<p>skb_header_pointer checks if the requested data is within the
linear area:</p>

<pre>        int hlen = skb_headlen(skb);

        if (offset + len &lt;= hlen)
                return skb-&gt;data + offset;</pre>

<p>When offset is within [INT_MAX-len+1..INT_MAX] the addition will
result in a negative number which is &lt;= hlen.</p>

<p>I couldn't trigger a crash on my AMD64 with 2GB of memory, but a
coworker tried on his x86 machine and it crashed immediately.</p>

<p>This patch fixes the check in skb_header_pointer to handle large
positive offsets similar to skb_copy_bits. Invalid data can still
be accessed using negative offsets (also similar to skb_copy_bits),
anyone using negative offsets needs to verify them himself.</p>

<p>Thanks to Thomas V?gtle &lt;thomas.voegtle@coreworks.de&gt; for verifying the
problem by crashing his machine and providing me with an Oops.</p>

</li>

<li>

<p>[NETFILTER]: Fix deadlock in ip6_queue</p>

<p>Already fixed in ip_queue, ip6_queue was missed.</p>

</li>

<li>

<p>[NETFILTER]: Fix potential memory corruption in NAT code (aka memory NAT)</p>

<p>The portptr pointing to the port in the conntrack tuple is declared static,
which could result in memory corruption when two packets of the same
protocol are NATed at the same time and one conntrack goes away.</p>

</li>

<li>

<p>[NETFILTER]: Wait until all references to ip_conntrack_untracked are dropped on
unload</p>

<p>Fixes a crash when unloading ip_conntrack.</p>

</li>

<li>

<p>[XFRM]: Fix possible overflow of sock->sk_policy</p>

<p>Spotted by, and original patch by, Balazs Scheidler.</p>

</li>

<li>

<p>[PATCH] bio_clone fix</p>

<p>Fix bug introduced in 2.6.11-rc2: when we clone a BIO we need to copy over the
current index into it as well.</p>

<p>It corrupts data with some MD setups.</p>

<p>See <a href="http://bugzilla.kernel.org/show_bug.cgi?id=4946">http://bugzilla.kernel.org/show_bug.cgi?id=4946</a></p>

<p>Huuuuuuuuge thanks to Matthew Stapleton &lt;matthew4196@gmail.com&gt; for doggedly
chasing this one down.</p>

</li>

<li>

<p>sys_get_thread_area does not memset to 0 its struct user_desc info before
copying it to user space...  since sizeof(struct user_desc) is 16 while the
actual datas which are filled are only 12 bytes + 9 bits (across the
bitfields), there is a (small) information leak.i</p>

<p>This was already committed to Linus' repository.</p>

</li>

<li>

<p>[VLAN]: Fix early vlan adding leads to not functional device</p>

<p>OK, I can see what's happening here. eth0 doesn't detect link-up until
after a few seconds, so when the vlan interface is opened immediately
after eth0 has been opened, it inherits the link-down state. Subsequently
the vlan interface is never properly activated and are thus unable to
transmit any packets.</p>

<p>dev-&gt;state bits are not supposed to be manipulated directly. Something
similar is probably needed for the netif_device_present() bit, although
I don't know how this is meant to work for a virtual device.</p>

</li>

<li>

<p>powernow-k8 requires that a data structure for each core be created in the
_cpu_init function call. The cpufreq infrastructure doesn't call _cpu_init
for the second core in each processor. Some systems crashed when _get was
called with an odd-numbered core because it tried to dereference a NULL
pointer since the data structure had not been created.</p>

<p>The attached patch solves the problem by initializing data structures for
all shared cores in the _cpu_init function. It should apply to 2.6.12-rc6
and has been tested by AMD and Sun.</p>

</li>

</ul>

<p>Several people posted their approval of various patches; no one had any
objections.</p>

</section>

<section
  title="SMB Maintainership"
  subject="Is anyone maintaining the smb filesystem?"
  archive="http://groups.google.com/group/mailing.unix.samba/msg/4f0c9a0cb6435769?hl=en"
  posts="5"
  startdate="03 Aug 2005 08:03:04 -0800"
  enddate="04 Aug 2005 08:22:10 -0800"
>
<topic>FS: smbfs</topic>
<topic>MAINTAINERS File</topic>
<topic>Samba</topic>

<mention>Urban Widmark</mention>

<p>Adrian Bunk asked:</p>

<quote who="Adrian Bunk">

<p>Is anyone maintaining the smb filesystem in the Linux kernel?</p>

<p>Emails to the Email address urban@teststation.com of Urban Widmark that
is listed in MAINTAINERS are bouncing.</p>

<p>Can anyone tell how to reach Urban and/or whether anyone is currently
maintaining smbfs?</p>

</quote>

<p>Tvrtko A. Ursulin replied, <quote who="Tvrtko A. Ursulin">It probably
won't help you much, but I had the same problem few months ago. There was
a bug in smbfs which I tried to discuss with someone, and after failing
to contact the maintainer, I sent the fix to Linus. I don't think even he
managed to get a response from Urban or someone else. The fix went in so I
stopped chasing it. So it looks like smbfs is not maintained.</quote></p>

</section>

</kc>

