On Sat, Dec 09, 2006 at 12:38:17PM -0800, Andrew Morton wrote:
> On Sun, 10 Dec 2006 06:59:10 +1100
> Benjamin Herrenschmidt <[EMAIL PROTECTED]> wrote:
> > Why would I prevent the framebuffer from initializing (and thus a
> > console to be displayed at all on many machines) just because for some
>
On Sat, Dec 09, 2006 at 01:58:29PM -0800, Andrew Morton wrote:
> On Sat, 9 Dec 2006 22:44:53 +0100
> Olivier Galibert <[EMAIL PROTECTED]> wrote:
> > Hmmm, I don't understand. Which is the bug, having a sysfs file
> > creation fail or going on if it happens?
>
>
On Tue, Dec 12, 2006 at 11:44:18AM -0700, Andrew Robinson wrote:
> When I said hibernate, I did mention it was to disk, not to ram.
Suspend to disk is not trustable on Linux, and does not look like it
will be any time soon. Suspend to ram has a better chance of becoming
reliable, but at that poin
On Thu, Dec 14, 2006 at 10:56:03AM +0100, Hans-Jürgen Koch wrote:
> A small German manufacturer produces high-end AD converter cards. He sells
> 100 pieces per year, only in Germany and only with Windows drivers. He would
> now like to make his cards work with Linux. He has two driver programmers
>
On Thu, Dec 14, 2006 at 11:11:33AM -0500, Dave Jones wrote:
> On Thu, Dec 14, 2006 at 04:05:14PM +0100, Adrian Bunk wrote:
> > If a kernel developer or a competitor sends a cease&desist letter to
> > such a distribution, the situation changes from a complicated "derived
> > work" discussion to
;
}
}
*offset += size;
return size;
}
case MODE_MAILBOX: {
size_t cur_size = size;
for(;;) {
unsigned int val;
if(get_user(val, (unsigned int *)buf))
return -EFAULT;
iiadc64_mailbox_write(is.access_mbox, val);
buf += sizeof(unsigned int
Is there a way to know if there has been I/O error(s) on a specific
disk or partition since boot other than parsing dmesg and hoping it's
both still there and in the expected format?
Of course that's if the error didn't kill the system in the first
place :-)
OG.
-
To unsubscribe from this list
On Sun, Jan 07, 2007 at 11:42:09AM -0800, Jesse Barnes wrote:
> This patch updates Oliver's MMConfig bridge detection patches with support
> for 915G bridges. It seems to work ok on my 915GM laptop.
Looks ok to me.
> I also tried adding 965 support, but it doesn't work (at least not on my
> G96
On Sun, Jan 07, 2007 at 11:44:16AM -0800, Jesse Barnes wrote:
> For reference, here's the probe routine I tried for 965, probably something
> dumb wrong with it that I'm not seeing atm.
It shouldn't have mattered in your case, but base_address is limited
to 32bits. There is a 32 bits reserved zo
er chips. But since I didn't have platforms
> to test such additions on, they're left out for now.
>
> Signed-off-by: Jesse Barnes <[EMAIL PROTECTED]>
Signed-off-by: Olivier Galibert <[EMAIL PROTECTED]>
Andrew, you sent me a series of emails to tell me the patches h
Ok, here you go, what about that? I'll be able to test it on i386 on
monday, not before. It's hard to doa full 32bits install remotely :-)
OG.
>From 9703313602daaac65e41210444b2ce20b6e340b6 Mon Sep 17 00:00:00 2001
From: Olivier Galibert <[EMAIL PROTECTED]>
Date: Sun, 2
On Sun, Nov 26, 2006 at 08:28:04PM +0100, Andi Kleen wrote:
> On Sunday 26 November 2006 14:15, Olivier Galibert wrote:
> > Ok, here you go, what about that? I'll be able to test it on i386 on
> > monday, not before. It's hard to doa full 32bits install remotely :-)
>
On Mon, Nov 27, 2006 at 08:07:48PM +0100, Andi Kleen wrote:
> Is that with just the code movement patch or your feature patch
> added too? If the later can you test it with only code movement
> (and compare against vanilla kernel). at least code movement
> only should behave exactly the same as unp
On Mon, Nov 27, 2006 at 09:24:06PM +0100, Olivier Galibert wrote:
> On Mon, Nov 27, 2006 at 08:07:48PM +0100, Andi Kleen wrote:
> > Is that with just the code movement patch or your feature patch
> > added too? If the later can you test it with only code movement
> > (and co
On Sun, Jun 24, 2007 at 09:57:24PM +0100, Alan Cox wrote:
> > Sory Alan but I don't want philosophical/historical discuss.
> > Try to answer on question "ALSA or OSS ?" using *only* technical arguments.
>
> We dropped OSS for ALSA for technical reasons. Those being that ALSA
> - has a better audio
On Mon, Jun 25, 2007 at 02:40:23PM +0200, Jan Engelhardt wrote:
>
> On Jun 25 2007 14:31, Takashi Iwai wrote:
> >> It was started in time when most cheap sound cards was without hw mixer.
> >> And .. when today you use ALSA on sound card without hw mixer still all
> >> this (past ?) problems are
On Mon, Jun 25, 2007 at 02:31:08PM +0200, Takashi Iwai wrote:
> So, do you mean the soft-mixing is the biggest issue? That's just a
> part of a design issue, and if we want to go to that way, the
> impelemtation would be trivial, regardless on ALSA or not. Totally
> irrelevant argument regarding
On Mon, Jun 25, 2007 at 02:58:02PM +0200, Takashi Iwai wrote:
> Hm... I don't agree much with the virtual relay device solution.
> I once experimentally implemented an ALSA-OSS virtual kernel driver.
> But, it just gives more complexity.
So instead you move the complexity in the library where it
On Thu, Jun 14, 2007 at 09:20:35PM -0400, Rob Landley wrote:
> Why do you keep saying "upgraded" to GPLv3? How is it an improvement to move
> from a small, simple, elegant, and tested implementation to something that's
> more complicated, less elegant, less coherent, totally untested, and full o
On Tue, May 29, 2007 at 10:03:32PM -0600, Robert Hancock wrote:
> -Validate that the area is reserved even if we read it from the
> chipset directly and not from the MCFG table. This catches the case
> where the BIOS didn't set the location properly in the chipset and
> has mapped it over other thi
On Wed, May 23, 2007 at 02:20:23PM -0700, Jesse Barnes wrote:
> On Wednesday, May 23, 2007 1:56 pm Linus Torvalds wrote:
> > Ehh. Even for PCIe, why not use the normal accesses for the first 256
> > bytes? Problem solved.
>
> Ok, this patch also works. We still need to enable mmconfig space for
On Thu, Mar 22, 2007 at 02:33:14PM +, Al Viro wrote:
> Correction: current ABI is crap. To set the thing up you need to open
> it and issue an ioctl. Which is a bloody bad idea, for obvious reasons...
Agreed. What would be a right way? Global device ala ptmx/tun/tap?
New syscall? Somethin
On Wed, Apr 04, 2007 at 07:15:32PM +0100, Russell King wrote:
> *However* you still run into the issue that you do not know how many
> serial ports you will need to register a tty driver with the tty layer.
> Solve that technical problem and the idea of having a single namespace
> for chosen serial
Sorry for replying to Alan's reply, I missed the original mail.
> > +#define ata_id_has_AN(id) \
> > + ((id[76] && (~id[76])) & ((id)[78] & (1 << 5)))
(a && ~a) & (b & 32)
I don't think that does what you think it does, because at that point
it's a funny way to write 0 ((0 or 1) binary-and (0
On Tue, Apr 24, 2007 at 08:49:04AM -0700, Kristen Carlson Accardi wrote:
> On Tue, 24 Apr 2007 12:23:04 +0200
> Olivier Galibert <[EMAIL PROTECTED]> wrote:
>
> > Sorry for replying to Alan's reply, I missed the original mail.
> >
> > > > +#define ata_
On Tue, Apr 24, 2007 at 01:53:27PM -0700, Kristen Carlson Accardi wrote:
> Check to see if an ATAPI device supports Asynchronous Notification.
> If so, enable it.
>
> changes from last version:
> * fix typo in ata_id_has_AN and make word 76 test more clear
> * If we fail to set the AN feature, ju
On Tue, Apr 24, 2007 at 04:41:58PM -0700, Linus Torvalds wrote:
> How many different magic ioctl's does the thing introduce? Is it really
> just *two* entry-points (and how simple are they, interface-wise), and
> nothing else?
Aren't you a little late to the party here? The userland version is
On Wed, Apr 25, 2007 at 08:16:51PM +0100, Matt Sealey wrote:
> > +#define ata_id_has_AN(id) \
> > + ( (((id)[76] != 0x) && ((id)[76] != 0x)) && \
> > + ((id)[78] & (1 << 5)) )
>
> ??
>
> > --- 2.6-git.orig/include/linux/libata.h
> > +++ 2.6-git/include/linux/libata.h
> > @@ -136,6
On Wed, Apr 25, 2007 at 11:50:45AM -0700, Linus Torvalds wrote:
> .. but if the alternative is a feature that just isn't worth it, and
> likely to not only have its own bugs, but cause bugs elsewhere? (And yes,
> I believe STD is both of those. There's a reason it's called "STD". Go
> to google
On Thu, Apr 26, 2007 at 01:09:53PM +0200, Pavel Machek wrote:
> #define SNAPSHOT_SET_IMAGE_SIZE _IOW(SNAPSHOT_IOC_MAGIC, 6,
> unsigned long)
So I'm not supposed to be able to suspend the 16Gb-ram, 32bits servers
I have here?
OG.
-
To unsubscribe from this list: send the line "uns
On Fri, Apr 27, 2007 at 06:50:56AM +1000, Nigel Cunningham wrote:
> I'm perfectly willing to think through some alternate approach if you
> suggest something or prod my thinking in a new direction, but I'm afraid
> I just can't see right now how we can achieve what you're after.
Ok, what about thi
On Thu, Apr 26, 2007 at 03:49:51PM -0700, David Lang wrote:
> swap partitions are limited to 2G (or at least they were a couple of months
> ago when I last checked). I also don't want to run the risk of having a box
> try to _use_ 16G worth of swap. I'd rather have the box hit OOM first.
They ar
On Wed, Apr 04, 2007 at 12:14:34PM +0100, Alan Cox wrote:
> > If you want hierarchy, create it:
> >
> > /sys/blah/serial/controllerX/portY
> >
> > and keeping them all under the ttyS? major keeps the simple
> > cases working sanely too.
>
> Currently yes you could do that, but that would break a
On Sun, Apr 29, 2007 at 08:14:37PM -0600, Robert Hancock wrote:
> -Validate that the area is reserved even if we read it from the
> chipset directly and not from the MCFG table. This catches the case
> where the BIOS didn't set the location properly in the chipset and
> has mapped it over other thi
On i945, a mmconfig range hitting the f000- zone conflicts
with the APIC registers and others. Consider it invalid.
On E7520, values and f000 for the window register are defined
invalid in the documentation.
---
I haven't seen a bios use these values, but who trusts biosen thes
On Wed, May 02, 2007 at 11:52:36AM +0200, Andi Kleen wrote:
> On Wednesday 02 May 2007 02:50:11 Olivier Galibert wrote:
> > On i945, a mmconfig range hitting the f000- zone conflicts
> > with the APIC registers and others. Consider it invalid.
> >
> > On
Wasn't/Isn't the 4G/4G memory layout for 32 bits essentially KPTI?
OG.
On Thu, Jan 11, 2018 at 12:32 AM, Pavel Machek wrote:
> Hi!
>
>> The one thing I want to do now that Meltdown and Spectre are public,
>> is to give a *big* shout-out to the x86 people, and Thomas Gleixner in
>> particular
Wouldn't the time taken by an easy syscall like getuid be a clear indicator?
OG.
On Thu, Jan 11, 2018 at 8:17 PM, Dave Hansen
wrote:
> On 01/11/2018 11:07 AM, Borislav Petkov wrote:
>> On Thu, Jan 11, 2018 at 10:57:51AM -0800, Dave Hansen wrote:
>>> I'd love to have a tool that tells you for
On Wed, Sep 26, 2007 at 07:57:38PM +0930, David Newall wrote:
> As has been said, there are thousands of ways to break out of a chroot.
> It's just that one of them should not be that chroot lets you walk out.
chroot does not allow you to walk out if you're in. It only allows
you to walk outs
On Wed, Sep 26, 2007 at 08:43:44PM +0930, David Newall wrote:
> Olivier Galibert wrote:
> >chroot does not allow you to walk out if you're in.
>
> You're mistaken. Or more properly, further use of chroot lets you walk
> out. This really has been said be
On Mon, Oct 01, 2007 at 09:04:44AM -0700, Linus Torvalds wrote:
> For example, you security guys still debate "inodes" vs "pathnames", as if
> that was an either-or issue.
>
> Quite frankly, I'm not a security person, but I can tell a bad argument
> from a good one. And an argument that says "in
On Fri, Aug 24, 2007 at 05:43:47AM -0700, SL Baur wrote:
> Who uses code like this, by the way?
People who think Posix is an example to follow maybe? Not sure if it
would go past the maintainers though :-)
# define PTHREAD_MUTEX_INITIALIZER \
{ { 0, 0, 0, 0, 0, { 0 } } }
# ifdef __USE_GNU
# d
On Tue, Apr 21, 2015 at 12:31 PM, Greg Kroah-Hartman
wrote:
> Bringing up SCM_RIGHTS means that this is not going to be a bus system
> at all. One principal design goal is to _not_ have peer-to-peer
> connections between all communicating parties, but rather one connection
> to a central componen
On Sat, Jul 14, 2012 at 12:33:51AM +0200, Jesper Juhl wrote:
> How about we start cutting down on the options and start saying "a Linux
> system will provide feature x and y - always ...".
> Stuff like (and I'm just pulling random stuff out here) - ASLR, seccomp,
> 250HZ minimum etc etc.. We coul
On Wed, Jul 9, 2014 at 7:49 PM, Sebastian Andrzej Siewior
wrote:
> + * The lock assumption made here is none because runtime-pm suspend/resume
> + * callbacks should not be invoked there is any operation performed on the
> port.
I think there's a missing "if"?
Best,
OG.
--
To unsubscribe fro
Hi,
Beware that could be opening the door to information leaks for a very
small gain (most syscalls are not getuid).
Best,
OG.
On Sat, Mar 28, 2015 at 1:34 AM, Denys Vlasenko
wrote:
> On Fri, Mar 27, 2015 at 9:00 PM, Linus Torvalds
> wrote:
>> On Fri, Mar 27, 2015 at 7:25 AM, Denys Vlase
On Tue, Oct 3, 2017 at 5:22 AM, Adam Borowski wrote:
> Well, what about just \n then? Unlike all the others which are relatively
> straightforward, \n requires -print0 which not all programs implement, and
> way too many people consider too burdensome to use.
If you don't use -print0, you're vul
101 - 147 of 147 matches
Mail list logo
