2015-09-21 21:45 GMT+03:00 Dave Hansen :
>
> From: Dave Hansen
>
> There was a report that my patch:
>
> inotify: actually check for invalid bits in sys_inotify_add_watch()
>
> broke CRIU.
>
> The reason is that CRIU looks up raw flags in /proc/$pid/fdinfo/*
> to figure out how to rebuild
On Mon, Sep 21, 2015 at 11:45:01AM -0700, Dave Hansen wrote:
>
> From: Dave Hansen
>
> There was a report that my patch:
>
> inotify: actually check for invalid bits in sys_inotify_add_watch()
>
> broke CRIU.
>
> The reason is that CRIU looks up raw flags in /proc/$pid/fdinfo/*
> to fig
Acked-by: Eric Paris
On Mon, 2015-09-21 at 11:45 -0700, Dave Hansen wrote:
> From: Dave Hansen
>
> There was a report that my patch:
>
> inotify: actually check for invalid bits in
> sys_inotify_add_watch()
>
> broke CRIU.
>
> The reason is that CRIU looks up raw flags in /proc/$pid/fd
From: Dave Hansen
There was a report that my patch:
inotify: actually check for invalid bits in sys_inotify_add_watch()
broke CRIU.
The reason is that CRIU looks up raw flags in /proc/$pid/fdinfo/*
to figure out how to rebuild inotify watches and then passes those
flags directly back
From: Ingo Molnar <[EMAIL PROTECTED]>
add the kernel generic bits - these are present even if !CONFIG_ASYNC_SUPPORT.
Signed-off-by: Ingo Molnar <[EMAIL PROTECTED]>
Signed-off-by: Arjan van de Ven <[EMAIL PROTECTED]>
---
fs/exec.c |4
include/linux/sched.h | 23
From: Ingo Molnar <[EMAIL PROTECTED]>
add the kernel generic bits - these are present even if !CONFIG_ASYNC_SUPPORT.
Signed-off-by: Ingo Molnar <[EMAIL PROTECTED]>
Signed-off-by: Arjan van de Ven <[EMAIL PROTECTED]>
---
fs/exec.c |4
include/linux/sched.h | 23
From: Ingo Molnar <[EMAIL PROTECTED]>
add the kernel generic bits - these are present even if !CONFIG_ASYNC_SUPPORT.
Signed-off-by: Ingo Molnar <[EMAIL PROTECTED]>
Signed-off-by: Arjan van de Ven <[EMAIL PROTECTED]>
---
include/linux/sched.h | 23 ++-
kernel/exit.c
From: Ingo Molnar <[EMAIL PROTECTED]>
add the kernel generic bits - these are present even if !CONFIG_ASYNC_SUPPORT.
Signed-off-by: Ingo Molnar <[EMAIL PROTECTED]>
Signed-off-by: Arjan van de Ven <[EMAIL PROTECTED]>
---
include/linux/sched.h |7 ++-
kernel/exit.c |3 +++
kern
> No, that only tells you the size of a long under the compiler you used.
> If you are on an Intel IA64 (64 bit kernel) but you compile with gcc
> for ix86 (32 bit userspace) then sizeof(long) is 4. IA64 runs both
> native and ix86 code, sizeof(any userspace field) tells you nothing
> about the k
On Mon, 27 Nov 2000, Chad Schwartz wrote:
> int main(void) {
> printf("Size of an unsigned long is %d bytes\n",sizeof(unsigned long));
> return(0);
> }
>
> That simple program will tell you that an unsigned long is 4 bytes, or 8
> bytes.
>
> It is then a safe assumption - that if yo
On Mon, 27 Nov 2000 07:36:22 -0600 (CST),
Chad Schwartz <[EMAIL PROTECTED]> wrote:
>int main(void) {
> printf("Size of an unsigned long is %d bytes\n",sizeof(unsigned long));
> return(0);
>}
>
>That simple program will tell you that an unsigned long is 4 bytes, or 8
>bytes.
>
>It is t
int main(void) {
printf("Size of an unsigned long is %d bytes\n",sizeof(unsigned long));
return(0);
}
That simple program will tell you that an unsigned long is 4 bytes, or 8
bytes.
It is then a safe assumption - that if you get back '8', that you're
running a 64bit kernel, on a
l.
> > And I want to have the kernel bits, not the processor bits.
>
> Solaris runs 32-bit kernels on 64-bit UltraSPARCs
> (up to Solaris version 2.6)
>
> So yes, something like that MAY be possible in case
> of ia64, but somehow I doubt...
It de
sor info you see at /proc/cpuinfo
> Can't I run a i386 kernel on a ia64 machine? I know something like this
> from HP-UX. You can choose between a 32 and a 64 bit kernel when
> installing, so knowing that you have a 64 bit capable machine does not
> say that you have a 64 bit kernel.
&g
when installing, so knowing
that you have a 64 bit capable machine does not say that you have a 64 bit
kernel.
And I want to have the kernel bits, not the processor bits.
Matti Aarnio <[EMAIL PROTECTED]> wrote:
> On Wed, Nov 22, 2000 at 09:25:46AM +0100, 64738 wrote:
> > Is there a
On Wed, Nov 22, 2000 at 09:25:46AM +0100, 64738 wrote:
> Hi.
>
> Is there a syscall or something that can tell me whether I'm working on a 32-
> or a 64-bit kernel?
uname(2)
It gives out various strings from which you must then deduce,
what kind of kernel is needed to r
Hi.
Is there a syscall or something that can tell me whether I'm working on a 32-
or a 64-bit kernel?
Greeting,
Alain
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
Please read the FAQ at http://www.tux.org/lkml/
Hi.
Is there a syscall or something that can tell me whether I'm working on a 32-
or a 64-bit kernel?
Greeting,
Alain
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
Please read the FAQ at http://www.tux.org/lkml/
18 matches
Mail list logo
