Jeff Chua | 1 May 2011 01:08
Picon

Re: [PATCH] staging: r8712u: Fix driver to support ad-hoc mode

On Sat, Apr 30, 2011 at 8:21 PM, clemens fischer
<ino-news <at> spotteswoode.dnsalias.org> wrote:
>> clemens fischer:
> Whatever I did late in the past night: sleeping ten hours helped a lot!
> I can now confirm that "r8712u" works in Ad-hoc mode using
> "wpa_supplicant(8)", it gets its IP from DHCP, connects everywhere and
> lets me get spam and all that.

Clemens,

Glad to head that!

> I still wish "r8712u" would let me use wireless-tools/iwconfig, but
> I can live with "wpa_supplicant(8)".

You wish just came true. To use plain iwconfig with wpa_supplicant,
here's what you need to do ...
just remember that the "order" is important ... you must set the
encryption key "before" you bring up the interface!!! This applies to
non-realtek devices as well.

# modprobe r8712u
# iwconfig wlan0 key restricted your-encrypted-password-same-as-wpa-psk-string
# ifconfig wlan0 up   <-- this comes after you set up the encryption above!
# iwconfig wlan0 mode ad-hoc essid your-ssid
# ifconfig wlan0 your-ip
# dhcpd wlan0

Larry, thanks again for your help getting me started on this. The
device is working great!
(Continue reading)

Yinghai Lu | 1 May 2011 01:10

Re: [PATCH 08/25] x86, NUMA: trivial cleanups

On 04/30/2011 11:00 AM, Tejun Heo wrote:
> Hello,
> 
> On Sat, Apr 30, 2011 at 6:24 PM, Yinghai Lu <yinghai <at> kernel.org> wrote:
>> I posted two patches for
>> Kill no longer used struct bootnode.
>> Make setup_node_bootmem() static
> 
> Ah, okay.  Do you mind resending them to me?  I'll integrate it with
> the patchset.

Never mind. Do not want to waste your time to rebase your tree.

> 
>> Also setup_node_bootmem now is some misleading, could change to setup_node_data() ?
> 
> Sure, I don't like the current name either.  Do you mind sending a
> patch for that too?

ok, another mail.

Thanks

Yinghai Lu
Yinghai Lu | 1 May 2011 01:11

[PATCH] x86, numa: Rename setup_node_bootmem to setup_node_data


after using memblock to replace bootmem, that function only setup node_data
now.

Change the name to reflecting the real work.

Signed-off-by: Yinghai Lu <yinghai <at> kernel.org>

---
 arch/x86/mm/numa.c |    6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

Index: linux-2.6/arch/x86/mm/numa.c
===================================================================
--- linux-2.6.orig/arch/x86/mm/numa.c
+++ linux-2.6/arch/x86/mm/numa.c
 <at>  <at>  -189,8 +189,8  <at>  <at>  int __init numa_add_memblk(int nid, u64
 	return numa_add_memblk_to(nid, start, end, &numa_meminfo);
 }

-/* Initialize bootmem allocator for a node */
-static void __init setup_node_bootmem(int nid, u64 start, u64 end)
+/* Initialize NODE_DATA for a node on the local memory */
+static void __init setup_node_data(int nid, u64 start, u64 end)
 {
 	const u64 nd_low = PFN_PHYS(MAX_DMA_PFN);
 	const u64 nd_high = PFN_PHYS(max_pfn_mapped);
 <at>  <at>  -522,7 +522,7  <at>  <at>  static int __init numa_register_memblks(
 		}

(Continue reading)

Markus | 1 May 2011 02:38
Picon

Bug Report: 2.6.38 causes loop / lockup at boot

Summary: A vanilla net-install of Arch Linux or Debian Testing will result in an unbootable system

Keywords: Kernel, Boot, Lockup, Loop, ACPI

Kernel Version: 2.6.38.2 to .4

Environment: An old laptop (Gericom Overdose T2, around 2001) with a SiS 630 board, Pentium 3 1.26GHz, ACPI
1.0B compliant

Description:

After a fresh net-install of Arch Linux (i686), when the system is booted from harddisk for the first time,
it will loop these messages over and over, effectively making the system unusable. The messages never
make it into a log (and because they run by very fast, this is all I could glean). Happens with both kernels
2.6.38.2 and 2.6.38.3:

[<c11ec???>] ? acpi_add_single_object
[<c11ec???>] ? acpi_device_suspend

For 2.6.38.4, the messages change slightly:

[<c11ec???>] ? acpi_add_single_object
[<c11ed???>] ? unregister_acpi_bus_type

Something similar happens after installing Debian Stable (i386 LXDE) and updating to Testing, except
that the messages don't loop, but there's only about 10 of them before the system freezes up completely.

Fedora 15 beta with 2.6.38 booted fine.

------------------------------------
(Continue reading)

Yinghai Lu | 1 May 2011 02:43

Re: [PATCH] x86, NUMA: Fix empty memblk detection in numa_cleanup_meminfo()

On 04/30/2011 05:33 AM, Tejun Heo wrote:
> From: Yinghai Lu <yinghai <at> kernel.org>
> 
> numa_cleanup_meminfo() trims each memblk between low (0) and high
> (max_pfn) limits and discard empty ones.  However, the emptiness
> detection incorrectly used equality test.  If the start of a memblk is
> higher than max_pfn, it is empty but fails the equality test and
> doesn't get discarded.
> 
> Fix it by using >= instead of ==.
> 
> Signed-off-by: Yinghai Lu <yinghai <at> kernel.org>
> Signed-off-by: Tejun Heo <tj <at> kernel.org>
> ---
> So, something like this.  Does this fix the problem you see?
> 
> Thanks.
> 
>  arch/x86/mm/numa_64.c |    2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> Index: work/arch/x86/mm/numa.c
> ===================================================================
> --- work.orig/arch/x86/mm/numa.c
> +++ work/arch/x86/mm/numa.c
>  <at>  <at>  -191,7 +191,7  <at>  <at>  int __init numa_cleanup_meminfo(struct n
>  		bi->end = min(bi->end, high);
>  
>  		/* and there's no empty block */
> -		if (bi->start == bi->end) {
(Continue reading)

Harry Wei | 1 May 2011 03:21
Picon

Re: [Oops 1/2]Something wrong with copy_from_user() function

On Sat, Apr 30, 2011 at 11:13:10PM +0200, Jiri Kosina wrote:
> On Sat, 30 Apr 2011, Harry Wei wrote:
> 
> 
> wpa_set_keys() function (from staging drivers) in your kernel uses 
> copy_from_user() without proper bounds checking, and thus can overflow and 
> corrupt memory.
Hmmm, i see.

Thanks.
Harry Wei.
> 
Lucian Adrian Grijincu | 1 May 2011 03:35
Picon

[PATCH 00/69] faster tree-based sysctl implementation


Short description: sysctl is slow (bad algorithm); this patch series
makes it faster (without using more memory but with some limitations).

$ time modprobe dummy numdummies=N

Without this patch series :(
- ipv4 only
  -  N=1000  time= 0m 06s
  -  N=2000  time= 0m 30s
  -  N=4000  time= 2m 35s
- ipv4 and ipv6
  -  N=1000  time= 0m 24s
  -  N=2000  time= 2m 14s
  -  N=4000  time=10m 16s
  -  N=5000  time=16m 03s

With this patch series    :)
- ipv4 only
  -  N=1000  time=0.33s
  -  N=2000  time=1.25s
  -  N=4000  time=5.31s
- ipv4 and ipv6
  -  N=1000  time=0.41s
  -  N=2000  time=1.62s
  -  N=4000  time=7.64s
  -  N=5000  time=12.35s
  -  N=8000  time=36.95s

Tests were done with and without ipv6 with the same .config on
(Continue reading)

Lucian Adrian Grijincu | 1 May 2011 03:35
Picon

[PATCH 01/69] sysctl: remove .child from dev/parport/default

First patch in a series that will end with a rewrite of sysctl. The
new implementation needs to get rid of the .child field of ctl_table.

Same functionality, but a little more clarity.

MAINTAINERS says parport is "Orphan" and I don't have a parallel
port. I minimally tested this patch, but I don't know who to resort to
for an ACK.

Signed-off-by: Lucian Adrian Grijincu <lucian.grijincu <at> gmail.com>
---
 drivers/parport/procfs.c |   96 +++++++++++++++++++---------------------------
 1 files changed, 40 insertions(+), 56 deletions(-)

diff --git a/drivers/parport/procfs.c b/drivers/parport/procfs.c
index 3f56bc0..89b8b71 100644
--- a/drivers/parport/procfs.c
+++ b/drivers/parport/procfs.c
 <at>  <at>  -419,56 +419,6  <at>  <at>  parport_device_sysctl_template = {
 	}
 };

-struct parport_default_sysctl_table
-{
-	struct ctl_table_header *sysctl_header;
-	ctl_table vars[3];
-        ctl_table default_dir[2];
-	ctl_table parport_dir[2];
-	ctl_table dev_dir[2];
-};
(Continue reading)

Lucian Adrian Grijincu | 1 May 2011 03:35
Picon

[PATCH 03/69] sysctl: remove .child from dev/parport/PORT/devices/DEVICE

MAINTAINERS says parport is "Orphan" and I don't have a parallel
port => I cannot test that this patch works.

Signed-off-by: Lucian Adrian Grijincu <lucian.grijincu <at> gmail.com>
---
 drivers/parport/procfs.c |   56 ++++++++++------------------------------------
 1 files changed, 12 insertions(+), 44 deletions(-)

diff --git a/drivers/parport/procfs.c b/drivers/parport/procfs.c
index edeb012..350233e 100644
--- a/drivers/parport/procfs.c
+++ b/drivers/parport/procfs.c
 <at>  <at>  -370,17 +370,11  <at>  <at>  struct parport_device_sysctl_table
 {
 	struct ctl_table_header *sysctl_header;
 	ctl_table vars[2];
-	ctl_table device_dir[2];
-	ctl_table devices_root_dir[2];
-	ctl_table port_dir[2];
-	ctl_table parport_dir[2];
-	ctl_table dev_dir[2];
 };

 static const struct parport_device_sysctl_table
 parport_device_sysctl_template = {
-	.sysctl_header = NULL,
-	{
+	.vars = {
 		{
 			.procname 	= "timeslice",
(Continue reading)

Lucian Adrian Grijincu | 1 May 2011 03:35
Picon

[PATCH 05/69] sysctl: remove .child from dev/parport/PORT/devices/

Signed-off-by: Lucian Adrian Grijincu <lucian.grijincu <at> gmail.com>
---
 drivers/parport/procfs.c |   42 ++++++++++++++++++++++++++++--------------
 1 files changed, 28 insertions(+), 14 deletions(-)

diff --git a/drivers/parport/procfs.c b/drivers/parport/procfs.c
index e55b9b6..3bb5bed 100644
--- a/drivers/parport/procfs.c
+++ b/drivers/parport/procfs.c
 <at>  <at>  -248,6 +248,7  <at>  <at>  PARPORT_MAX_SPINTIME_VALUE;

 struct parport_sysctl_table {
 	struct ctl_table_header *sysctl_header;
+	struct ctl_table_header *devices_sysctl_header;
 	ctl_table vars[12];
 	ctl_table device_dir[2];
 };
 <at>  <at>  -291,11 +292,6  <at>  <at>  static const struct parport_sysctl_table parport_sysctl_template = {
 			.mode		= 0444,
 			.proc_handler	= do_hardware_modes
 		},
-		{
-			.procname = "devices",
-			.mode = 0555,
-			.child = NULL, /* child will point to .device_dir */
-		},
 #ifdef CONFIG_PARPORT_1284
 		{
 			.procname	= "autoprobe",
 <at>  <at>  -378,6 +374,14  <at>  <at>  int parport_proc_register(struct parport *port)
(Continue reading)


Gmane