linux-kernel - Re: cpu4096 + smp

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <488F3148.2050500@sgi.com>
Date:	Tue, 29 Jul 2008 08:03:36 -0700
From:	Mike Travis <travis@....com>
To:	Jiri Slaby <jirislaby@...il.com>
CC:	Ingo Molnar <mingo@...e.hu>,
	Linux kernel mailing list <linux-kernel@...r.kernel.org>
Subject: Re: cpu4096 + smp_affinity breakage

Jiri Slaby wrote:
> Hi,
> 
> I see cpu4096 branches in -tip. Do you know about
> /proc/irq/*/*smp_affinity (irq_affinity_read_proc,
> default_affinity_read) breakage with NR_CPUS=4096? Reading by `cat' from
> those files fails due to bitmap sent out is about 1150 bytes, but cat
> provides only 1024B sized buffer. Can you think about any fix for this?
> 
> Using file offset and utilize only portion of that buffer returned to
> the userspace will break atomicity I guess (does this matter?). If we
> get a snapshot, it would get old if some reader breaks up. And if we use
> per-reader buffer, we will be unable to free it. Any ideas?
> 
> I think the same problem is for not-at-once-writes.

The best alternate is to use cpulist_scnprintf but even this has
problems in the worst pathological case (where you want every other
cpu listed, e.g. only one of the two hyper threads).  Another alternate
would be to send only nr_cpu_ids mask bits [with obviously some way
for the user to discover what nr_cpu_ids is.]

There was strong objections to changing any of the /sys interfaces, but
I don't know what the rules are for the /proc interfaces.  And (iirc),
overflow was the user's responsibility.  How about using "dd bs=4k ..."?

Thanks,
Mike
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/