Regards,
Albert Bourla
PFIZER B.V Supply Chain Manager
Tel: +31(0)208080 880
ADDRESS: Rivium Westlaan 142, 2909 LD
Capelle aan den IJssel, Netherlands
Regards,
Albert Bourla
PFIZER B.V Supply Chain Manager
Tel: +31(0)208080 880
ADDRESS: Rivium Westlaan 142, 2909 LD
Capelle aan den IJssel, Netherlands
Regards,
Albert Bourla
PFIZER B.V Supply Chain Manager
Tel: +31(0)208080 880
ADDRESS: Rivium Westlaan 142, 2909 LD
Capelle aan den IJssel, Netherlands
quotation
Kind Regards,
Albert Bourla
PFIZER B.V Supply Chain Manager
Tel: +31(0)208080 880
ADDRESS: Rivium Westlaan 142, 2909 LD
Capelle aan den IJssel, Netherlands
,
Albert Bourla
PFIZER B.V Supply Chain Manager
Tel: +31(0)208080 880
ADDRESS: Rivium Westlaan 142, 2909 LD
Capelle aan den IJssel, Netherlands
ecially when enumeration USB3 failed then downgrade to USB2.
> If enable debug message, there are too many messages,
This is the reason why it is not a good solution, when I just need to
confirm what the enumeration result is.
--
Thanks,
Albert
On Fri, Jan 8, 2021 at 10:16 AM Peter Chen wrote:
>
This reverts commit 1cbfb8c4f62d667f6b8b3948949737edb92992cc.
The log of USB enumeration result is a useful log and only occupies
one line especially when USB3 enumeration failed and then downgrade
to USB2.
Signed-off-by: Albert Wang
---
drivers/usb/gadget/composite.c | 6 +++---
1 file
tps://www.kernel.org/doc/html/latest/admin-guide/reporting-bugs.html,
but it's still unclear to me whether a mail or a ticket in bugzilla is
preferred. Since this is just a documentation issue, maybe a mail is
fine.
/Albert
Good day , my name is Albert Khanukaev , i sent you a mail and there
was no response , please confirm that you did get this mail for more
details.
Regards.
Albert Khanukaev
From: Albert van der Linde
Add a failure injection capability to improve testing of fault-tolerance
in usages of user memory access functions.
Add CONFIG_FAULT_INJECTION_USERCOPY to enable faults in usercopy
functions. The should_fail_usercopy function is to be called by these
functions
From: Albert van der Linde
To test fault-tolerance of user memory access functions, introduce fault
injection to usercopy functions.
If a failure is expected return either -EFAULT or the total amount of
bytes that were not copied.
Reviewed-by: Akinobu Mita
Reviewed-by: Alexander Potapenko
From: Albert van der Linde
To test fault-tolerance of user memory acceses in x86, add support for
fault injection.
Make both put_user() and get_user() fail with -EFAULT, and clear_user()
fail by not clearing any bytes.
Reviewed-by: Akinobu Mita
Reviewed-by: Alexander Potapenko
Signed-off-by
From: Albert van der Linde
The goal of this series is to improve testing of fault-tolerance in
usages of user memory access functions, by adding support for fault
injection.
The first patch adds failure injection capability for usercopy
functions. The second changes usercopy functions to use
From: Albert van der Linde
To test fault-tolerance of user memory access functions, introduce fault
injection to usercopy functions.
If a failure is expected return either -EFAULT or the total amount of
bytes that were not copied.
Signed-off-by: Albert van der Linde
---
v2:
- removed partial
From: Albert van der Linde
Add a failure injection capability to improve testing of fault-tolerance
in usages of user memory access functions.
Add CONFIG_FAULT_INJECTION_USERCOPY to enable faults in usercopy
functions. The should_fail_usercopy function is to be called by these
functions
From: Albert van der Linde
The goal of this series is to improve testing of fault-tolerance in
usages of user memory access functions, by adding support for fault
injection.
The first patch adds failure injection capability for usercopy
functions. The second changes usercopy functions to use
From: Albert van der Linde
To test fault-tolerance of user memory acceses in x86, add support for
fault injection.
Make both put_user() and get_user() fail with -EFAULT, and clear_user()
fail by not clearing any bytes.
Signed-off-by: Albert van der Linde
---
v2:
- no significant changes
From: Albert van der Linde
To test fault-tolerance of usercopy accesses in x86, add support for
fault injection.
Make both put_user() and get_user() fail with -EFAULT, and clear_user()
fail by partially clearing fewer bytes.
Signed-off-by: Albert van der Linde
---
arch/x86/include/asm
From: Albert van der Linde
Add a failure injection capability to improve testing of fault-tolerance
in usages of user memory access functions.
Adds CONFIG_FAULT_INJECTION_USERCOPY to enable faults in usercopy
functions. By default functions are to either fail with -EFAULT or
return that no
From: Albert van der Linde
To test fault-tolerance of usercopy accesses, introduce fault injection
in usercopy functions.
Adds failure injection to usercopy functions. If a failure is expected
we return either the failure or the total amount of bytes. As many
usercopy functions can fail
From: Albert van der Linde
The goal of this series is to improve testing of fault-tolerance in
usages of user memory access functions, by adding support for fault
injection.
The first patch adds failure injection capability for usercopy
functions. The second changes usercopy functions to use
--
Hi!!
I want to especially thank Dr. Godsent .J. Yare for helping me get cured
of the Genital Herpes Virus. I was diagnosed last 2 summers and my
doctor said no cure for the virus. I was in big trouble until I saw this
sincere sounding YouTube post-https://youtu.be/Uw-l6rfcOl4 online
test
--
Hi!!
I want to especially thank Dr. Godsent .J. Yare for helping me get cured
of the Genital Herpes Virus. I was diagnosed last 2 summers and my
doctor said no cure for the virus. I was in big trouble until I saw this
sincere sounding YouTube post-https://youtu.be/Uw-l6rfcOl4 online
test
Hello,
I have a proposal of great benefit to discourse with you, kindly
respond back for more details.
Thanks
Mr. Albert
On 2019-10-08 15:38:15 -0700, Palmer Dabbelt wrote:
> On Fri, 20 Sep 2019 21:34:57 PDT (-0700), a...@brainfault.org wrote:
> > On Sat, Sep 21, 2019 at 6:30 AM Albert Ou wrote:
> >>
> >> This fixes an error with how the FDT blob is reserved in memblock.
> &g
page tables in two stages")
Signed-off-by: Albert Ou
---
Changes in v2:
* Changed variable identifier to dtb_early_pa per reviewer feedback.
* Removed whitespace change.
arch/riscv/mm/init.c | 12 +++-
1 file changed, 11 insertions(+), 1 deletion(-)
diff --git a/arch/riscv/mm/in
page tables in two stages")
Signed-off-by: Albert Ou
---
arch/riscv/mm/init.c | 13 -
1 file changed, 12 insertions(+), 1 deletion(-)
diff --git a/arch/riscv/mm/init.c b/arch/riscv/mm/init.c
index f0ba713..52d007c 100644
--- a/arch/riscv/mm/init.c
+++ b/arch/riscv/mm/i
--
Greetings,
I have an intending proposal for you please i need you to contact my
private
E-mail (dralbertddzo...@gmail.com) for more updates,
Best Wishes.
DR ALBERT ZONGO
--
--
Greetings,
I have an intending proposal for you please i need you to contact my
private
E-mail (dralbertddzo...@gmail.com) for more updates,
Best Wishes.
DR ALBERT ZONGO
--
On Thu, Apr 25, 2019 at 10:07 PM Andrew Morton
wrote:
>
> On Fri, 1 Feb 2019 21:39:59 +0100 Albert Vaca Cintora
> wrote:
>
> > Adds a readonly 'current_inotify_watches' entry to the user sysctl table.
> > The handler for this entry is a custom function that
On Fri, Feb 1, 2019 at 9:42 PM Albert Vaca Cintora wrote:
>
> Adds a readonly 'current_inotify_watches' entry to the user sysctl table.
> The handler for this entry is a custom function that ends up calling
> proc_dointvec. Said sysctl table already contains 'max_ino
re a finite resource, in a similar way to available file
descriptors. The motivation for this patch is to be able to set up
monitoring and alerting before an application starts failing because
it runs out of inotify watches.
Signed-off-by: Albert Vaca Cintora
Acked-by: Jan Kara
Reviewed-by: Ni
Adds a readonly 'current_inotify_watches' entry to the user sysctl table.
The handler for this entry is a custom function that ends calling
proc_dointvec.
Signed-off-by: Albert Vaca Cintora
---
kernel/ucount.c | 29 +
1 file changed, 29 insertions(+)
di
t of inotify watches.
Albert Vaca Cintora (1):
kernel/ucounts: expose current inotify watch count
kernel/ucount.c | 29 +
1 file changed, 29 insertions(+)
--
2.20.1
Dobrodelna loterija zmagovalec.
Vaš e-poštni naslov je pravkar zmaga (One Hundred in petdeset tisoč. Evrov) €
150.000,00 v programu UPLIFT International Charity. Zap: SP / 229 / 0-01 / 07 /
5-02 / EC. Lucky št: 9/11/13/24/40.
Za dodatne informacije in zahtevek stiku postopku;
CAPITAL CLAIM A
We got into the current situation for performance reasons, avoiding the costly
reload of CR3 that a hardware task switch would cause. It seems we'll be
loading CR3 now anyway, so it might be time to reconsider hardware
task switches.
The recent patches leave kernel entry/exit code mapped. Hardware
Good Day,
I'm Wong Shiu a staff of Wing Hang Bank
here in Hong Kong. Can i TRUST you in transferring-
$13,991,674 USD? If yes do get back to me with my private email:
wong.shiu...@accountant.com
Best Regards
ely reported ECC error.
Fixes: 02b88eea9f9c ("mtd: brcmnand: Add check for erased page bitflip")
Signed-off-by: Albert Hsieh
---
drivers/mtd/nand/brcmnand/brcmnand.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/mtd/nand/brcmnand/brcmnand.c
b/drivers/mtd/
pending transaction.
I am Albert Silva Neto, A Fund Manager with the Integrated Crystal Investment
Company. I am contacting you based on my personal interest to develop a mutual
business relationship with you in your country. The amount and terms of
executing the deal will be made known to you upon
This bug was introduced with SE Linux, 18 years ago. People have been
adding hacks to work around it as the bug bites them, but really the
bug ought to be fixed. Signals related to a tty are supposed to come
from the kernel. This got broken for pty devices. We now act as if
the signal is sent from
Hello,
DO YOU NEED FINANCIAL HELP? IF YES, CONTACT US VIA EMAIL: ( f-cs...@att.net ).
Thank you.
Albert James.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org
BT (NAND_BBT_NO_OOB) which also allows ECC modes
> which uses up to 60 bytes on 64 byte OOB
> - Removed custom (downstream) BBT pattern since BBT table won't be
> compatible anyway (due to the change above)
For the sake of regression testing:
Tested-by: Albert ARIBAUD
> + /* first scan to find the device and get the page size */
> + if (nand_scan_ident(mtd, 1, NULL)) {
> + err = -ENXIO;
> + goto error;
> + }
> +
> + vf610_nfc_init_controller(nfc);
> +
> + /* Bad block options. */
> +
Hi Stefan,
Le Thu, 30 Jul 2015 19:00:38 +0200, Stefan Agner a
écrit :
> Hi Albert,
>
> On 2015-07-30 18:13, Albert ARIBAUD wrote:
> > Hi Stefan,
> >
> > Le Mon, 27 Jul 2015 18:42:41 +0200, Stefan Agner a
> > écrit :
> >
> >> This driver supp
ror;
> + }
Placing the call to vf610_nfc_init_controller() here, after the call
to nand_scan_ident() rather than before it, fixed the issue for me.
Cordialement,
Albert ARIBAUD
3ADEV
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a mes
Frieden
und etwas sehr Positives ist dabei, gerade jetzt, um Ihr Leben passieren
und das Leben anderer durch Sie, wenn nur Sie sorgfältig zu lesen und zu
verdauen die Nachricht unten.
Bevor ich weiter gehen, lassen Sie mich Ihnen ein wenig von meiner
Biographie, ich bin Mutter Evelyn Albert, 82
Signed-off-by: Albert Pool
Reported-by: Michael Landrum
---
drivers/net/wireless/ath/ar5523/ar5523.c |1 +
1 file changed, 1 insertion(+)
diff --git a/drivers/net/wireless/ath/ar5523/ar5523.c
b/drivers/net/wireless/ath/ar5523/ar5523.c
index 17d7fec..280fc3d 100644
--- a/drivers/net
This adds the USB ID of the On Networks N300MA, clone of Netgear WNA3100M.
Signed-off-by: Albert Pool
Reported-by: Ana Rey
---
drivers/net/wireless/rtlwifi/rtl8192cu/sw.c |1 +
1 file changed, 1 insertion(+)
diff --git a/drivers/net/wireless/rtlwifi/rtl8192cu/sw.c
b/drivers/net/wireless
This adds the USB ID of the On Networks N300MA, clone of Netgear WNA3100M.
Signed-off-by: Albert Pool
Reported-by: Ana Rey
---
drivers/net/wireless/rtlwifi/rtl8192cu/sw.c |1 +
1 file changed, 1 insertion(+)
diff --git a/drivers/net/wireless/rtlwifi/rtl8192cu/sw.c
b/drivers/net
From: Albert Graham <[EMAIL PROTECTED]>
Signed-off-by: Albert Graham <[EMAIL PROTECTED]>
[PATCH] V4L/DVB: SAA7134: Enable remote control support for Avermedia M102
This patch enabled the IR remote control for the Avermedia M102 (card=110),
which appears to be the same IR as
On Nov 29, 2007 4:40 PM, Eric W. Biederman <[EMAIL PROTECTED]> wrote:
> "Albert Cahalan" <[EMAIL PROTECTED]> writes:
>
> > On Nov 28, 2007 6:31 AM, Eric W. Biederman <[EMAIL PROTECTED]> wrote:
> >> Ingo Molnar <[EMAIL PROTECTED]> wr
On Nov 28, 2007 5:46 AM, Ingo Molnar <[EMAIL PROTECTED]> wrote:
> * Albert Cahalan <[EMAIL PROTECTED]> wrote:
> > On Nov 27, 2007 7:49 PM, Guillaume Chazarain <[EMAIL PROTECTED]> wrote:
> > > [EMAIL PROTECTED] wrote:
> > >
> > > > We ma
On Nov 28, 2007 6:31 AM, Eric W. Biederman <[EMAIL PROTECTED]> wrote:
> Ingo Molnar <[EMAIL PROTECTED]> writes:
> > * Albert Cahalan <[EMAIL PROTECTED]> wrote:
> >> On Nov 27, 2007 7:49 PM, Guillaume Chazarain <[EMAIL PROTECTED]> wrote:
> In a lot of w
existence, and programs relying on
> this interface will loudly break on older kernels, unlike with the
> proposed interface change.
>
> Ccing Albert Cahalan as he made the change to /proc/self in the first
> place:
Changing /proc/self is somewhat risky, and probably
undesirabl
he following interrupt, so HSM violation is triggered.
>
> The patch modifies HSM such that it keeps throwing away extra data as
> long as the drive asserts DRQ which is how IDE driver does it.
>
>From past experience, some dead ATAPI devices stuck in DRQ=1. We should
take care of su
On 7/14/07, David Miller <[EMAIL PROTECTED]> wrote:
From: "Albert Cahalan" <[EMAIL PROTECTED]>
Date: Sat, 14 Jul 2007 22:48:57 -0400
> A real constant-value PAGE_SIZE is useful and doable.
It's bogus to use it. The kernel can get recompiled
to arbitrary page siz
Olaf Hering writes:
On Sat, Jul 14, H. Peter Anvin wrote:
Olaf Hering wrote:
Declare PAGE_SIZE as getpagesize() for userspace.
PAGE_SIZE is used in resource.h and shm.h
I would think it would be better to not define it at all.
Several architectures already don't have PAGE_SIZE visible
to us
On 7/7/07, Satyam Sharma <[EMAIL PROTECTED]> wrote:
On 7/7/07, Albert Cahalan <[EMAIL PROTECTED]> wrote:
I had one share mounted, from XP to Linux, and wanted another.
At first I had an incorrect setting on the XP box, almost
certainly related to permissions. The mount fail
I had one share mounted, from XP to Linux, and wanted another.
At first I had an incorrect setting on the XP box, almost
certainly related to permissions. The mount failed of course.
Running "mount" showed that the filesystem was not mounted,
but apparently it didn't remain fully unmounted either.
Jeff Garzik wrote:
>>> I have patches from Alan (pata_sis FIFO whack, pata_dma option), Tejun,
>>> Albert and Kristen still to be reviewed. Will get to those on Friday,
>>> after the July 4th US holiday.tions(-)
>
>
> Just to be more specific, my to-review
new patch attached, thanks for the speedy review.
> >
> > This fix is also confirmed by somebody else, see
> > https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=243030
> >
> > It would be great if this could go into .22, although I appreciate it's
> > quite lat
Robert de Rooy wrote:
> Albert Lee wrote:
>
>> Mark Lord wrote:
>>
>>
>>> ...
>>>
>>> Mmm.. I don't know about the first failure there,
>>> but after that it gets into the "stuck DRQ" state
>>> which libata m
107
>
> ...
>
> Mmm.. I don't know about the first failure there,
> but after that it gets into the "stuck DRQ" state
> which libata makes no attempt to handle at present.
>
It seems the pata_pcmcia driver is using IRQ driven PIO. Maybe Robert
could
On 6/22/07, Arjan van de Ven <[EMAIL PROTECTED]> wrote:
> > > > and these methods also destroy yourself on any machine with a looser
> > > > cache coherency between I and D-cache
> > > >
> > > > for all but x86 you pretty much have to do the mprotect() between the
> > > > two states to deal
On 6/21/07, Pavel Machek <[EMAIL PROTECTED]> wrote:
> >> It's really not worth getting bothered by. Truth is, big
> >> giant
> >> pathnames break lots of stuff already, both kernel and
> >> userspace.
> >
> >> Just look in /proc for some nice juicy kernel breakage:
> >> cwd, exe, fd/*, maps, mou
On 6/22/07, Arjan van de Ven <[EMAIL PROTECTED]> wrote:
On Fri, 2007-06-22 at 01:56 -0400, Albert Cahalan wrote:
> On 6/21/07, Arjan van de Ven <[EMAIL PROTECTED]> wrote:
> > On Fri, 2007-06-08 at 02:35 -0400, Albert Cahalan wrote:
> > > Right now, Linux isn't
On 6/21/07, Arjan van de Ven <[EMAIL PROTECTED]> wrote:
On Fri, 2007-06-08 at 02:35 -0400, Albert Cahalan wrote:
> Right now, Linux isn't all that friendly to JIT emulators.
> Here are the problems and suggestions to improve the situation.
>
> There is an SE Linux e
On 6/20/07, H. Peter Anvin <[EMAIL PROTECTED]> wrote:
Albert Cahalan wrote:
> Look, let's back up a bit here. At a high level, what exactly do
> you imagine that this behavior was intended for? I suggest you
> list some examples of the attacks that are blocked.
>
&
On 6/20/07, H. Peter Anvin <[EMAIL PROTECTED]> wrote:
Albert Cahalan wrote:
> Putting this into the security policy was an error born of
> lazyness to begin with. Abuse of the security mechanism
> was easier than hacking the toolchain, ELF loader, etc.
>
> Either a binary ne
with Alan on this one.
On Tue, Jun 19, 2007 at 11:16:29PM -0400, Albert Cahalan wrote:
It does and it doesn't. There is not a reasonable way for a
user to mark an app as needing full self-modifying ability.
It's not like the executable stack, which can be set via the
ELF note marki
On 6/20/07, H. Peter Anvin <[EMAIL PROTECTED]> wrote:
William Lee Irwin III wrote:
> I presumed an ELF note or extended filesystem attributes were already
> in place for this sort of affair. It may be that the model implemented
> is so restrictive that users are forbidden to create new executa
On 6/19/07, William Lee Irwin III <[EMAIL PROTECTED]> wrote:
On Fri, Jun 08, 2007 at 02:35:22AM -0400, Albert Cahalan wrote:
Right now, Linux isn't all that friendly to JIT emulators.
Here are the problems and suggestions to improve the situation.
There is an SE Linux execmem restr
On 6/15/07, Pavel Machek <[EMAIL PROTECTED]> wrote:
[Albert Cahalan]
> It's really not worth getting bothered by. Truth is, big
> giant
> pathnames break lots of stuff already, both kernel and
> userspace.
> Just look in /proc for some nice juicy kernel breaka
Christoph Hellwig writes:
On Thu, Jun 14, 2007 at 04:36:09PM +0900, Kentaro Takeda wrote:
We limit the maximum length of any string data (such as
domainname and pathnames) to TOMOYO_MAX_PATHNAME_LEN
(which is 4000) bytes to fit within a single page.
Userland programs can obtain the amount of
On 6/13/07, Chris Mason <[EMAIL PROTECTED]> wrote:
On Wed, Jun 13, 2007 at 12:14:40PM -0400, Albert Cahalan wrote:
> On 6/13/07, Chris Mason <[EMAIL PROTECTED]> wrote:
> >On Wed, Jun 13, 2007 at 01:45:28AM -0400, Albert Cahalan wrote:
> >> * secure delete via
On 6/13/07, Chris Mason <[EMAIL PROTECTED]> wrote:
On Wed, Jun 13, 2007 at 01:45:28AM -0400, Albert Cahalan wrote:
> The usual wishlist:
>
> * inode-to-pathnames mapping
This one I'll code, it will help with inode link count verification. I
want to be able to detect
Neat! It's great to see somebody else waking up to the idea that
storage media is NOT to be trusted.
Judging by the design paper, it looks like your structs have some
alignment problems.
The usual wishlist:
* inode-to-pathnames mapping
* a subvolume that is a single file (disk image, database,
ount
- ignores t_dir, byte_block and so on.
Maybe we need a strategy to deal with incorrect passed-thru commands?
say,
- check and reject if something wrong
- mimimal check and warn/ignore, if it doesn't hurt command execution
--
albert
-
To unsubscribe from this list: send the line "un
On 6/8/07, Alan Cox <[EMAIL PROTECTED]> wrote:
> There is an SE Linux execmem restriction that enforces W^X.
This depends on whatever SELinux rulesets you are running. Its just a
good rule to have present that most programs shouldn't be self patching,
and then label those that do differently.
On 6/8/07, Eric Dumazet <[EMAIL PROTECTED]> wrote:
Albert Cahalan a écrit :
> Additions to better support JIT emulators:
>
> a. sysctl to set IPC_RMID by default
Not very good, this will break some apps.
As a sysctl, the admin gets to choose between
compatibility and san
On 6/8/07, Eric W. Biederman <[EMAIL PROTECTED]> wrote:
"Albert Cahalan" <[EMAIL PROTECTED]> writes:
> On 6/7/07, Eric W. Biederman <[EMAIL PROTECTED]> wrote:
>> So it looks to me like we need to do three things:
>> - Fix the inode number
>> -
Right now, Linux isn't all that friendly to JIT emulators.
Here are the problems and suggestions to improve the situation.
There is an SE Linux execmem restriction that enforces W^X.
Assuming you don't wish to just disable SE Linux, there are
two ugly ways around the problem. You can mmap a file
On 6/7/07, Eric W. Biederman <[EMAIL PROTECTED]> wrote:
So it looks to me like we need to do three things:
- Fix the inode number
- Fix the name on the hugetlbfs dentry to hold the key
- Add a big fat comment that user space programs depend on this
behavior of both the dentry name and the inod
On 6/7/07, Badari Pulavarty <[EMAIL PROTECTED]> wrote:
BTW, I agree with Eric that its would be nice to use shmid as part
of name instead of forcing to be as inode number. It should be
possible for pmap to workout shmid from "key" or name. Isn't it ?
It is not at all nice.
1. it's incompatibl
On 6/6/07, Andrew Morton <[EMAIL PROTECTED]> wrote:
On Wed, 6 Jun 2007 23:27:01 -0400 "Albert Cahalan" <[EMAIL PROTECTED]> wrote:
> Eric W. Biederman writes:
> > Badari Pulavarty <[EMAIL PROTECTED]> writes:
>
> >> Your recent cleanup to shm
Eric W. Biederman writes:
Badari Pulavarty <[EMAIL PROTECTED]> writes:
Your recent cleanup to shm code, namely
[PATCH] shm: make sysv ipc shared memory use stacked files
took away one of the debugging feature for shm segments.
Originally, shmid were forced to be the inode numbers and
they sh
David Schwartz writes:
[Aaron Wiebe]
open("/somefile", O_WRONLY|O_NONBLOCK|O_CREAT, 0644) = 1621 <0.415147>
How could they make any difference? I can't think of any
conceivable way they could.
Now, I'm a userspace guy so I can be pretty dense, but shouldn't a
call with a nonblocking flag r
Ingo Molnar writes:
looking over the list of our new generic APIs (see further below) i
think there are three important things that are needed for an API to
become widely used:
1) it should solve a real problem (ha ;-), it should be intuitive to
humans and it should fit into existing thing
On 5/29/07, Eric W. Biederman <[EMAIL PROTECTED]> wrote:
"Albert Cahalan" <[EMAIL PROTECTED]> writes:
> Jan Engelhardt writes:
-if(self_pid==1 && ADOPTED(processes[i]) && forest_type!='u')
+if(ADOPTED(processes[i]) && forest
Jan Engelhardt writes:
On Apr 10 2007 17:47, Jan Engelhardt wrote:
On Apr 8 2007 20:57, Oleg Nesterov wrote:
Anyway, re-parenting to swapper breaks pstree, it doesn't
show kernel threads. And if ->parent == /sbin/init, we can't
remove us from ->children (unless we forbid sub-thread-of-init
ex
Robin Holt writes:
On Mon, Apr 09, 2007 at 08:36:21AM -0600, Eric W. Biederman wrote:
Robin Holt <[EMAIL PROTECTED]> writes:
I would say this is more a benefit than a problem. With a couple
of these systems we are testing, the number of kernel threads is
far greater than the number of user p
Why can we still not do this?
It's a stupid restriction. Security isn't a reason;
we have SE Linux policy and auditing to take
care of any issues. Heck, SE Linux policy could
even deny this feature for the truly paranoid.
Writing to /dev/* to update timestamps is surely
a worse security situatio
On 5/19/07, Segher Boessenkool <[EMAIL PROTECTED]> wrote:
[Albert Cahalan]
> Set MMCR0[TBEE], set MMCR0[PMXE], and choose a TBL bit via
> MMCR0[TBSEL].
That's the performance monitor, which could very well be
in use already (for performance monitoring stuff, who
would have
On 5/18/07, Sergei Shtylyov <[EMAIL PROTECTED]> wrote:
Albert Cahalan wrote:
>>> Sure, but is there any utility in registering more than the
>>> decrementer on PPC?
>> Not yet. I'm not sure I know any other PPC CPU facility fitting
>> for clockevents
Sergei Shtylyov writes:
Kumar Gala wrote:
[Sergei Shtylyov]
Kumar Gala wrote:
I haven't looked at all the new clock/timer code, is there any
utility in having support for more than one clock source?
Of course, you may register as many as you like.
Sure, but is there any utility in regist
Please don't forget the immutable bit. ("man lsattr")
Having both, BSD-style, would be even better.
The immutable bit is important for working around
software bugs and "features" that damage files.
I also can't find xattr support.
-
To unsubscribe from this list: send the line "unsubscribe linux-
On 5/9/07, Andrey Borzenkov <[EMAIL PROTECTED]> wrote:
On Wednesday 09 May 2007, Albert Cahalan wrote:
...
On May 8 2007 00:43, Albert Cahalan wrote:
Fix: the vfat driver should use the 8.3 name for such files.
...
It's not appropriate for vfat, HPFS, JFS, or NTFS. All of those
On 5/8/07, Jan Engelhardt <[EMAIL PROTECTED]> wrote:
On May 8 2007 00:43, Albert Cahalan wrote:
> Fix: the vfat driver should use the 8.3 name for such files.
Or the 31-character ISO Level 1(?).
That might be appropriate for a similar problem on CD-ROM
filesystems. (when
[EMAIL PROTECTED], [EMAIL PROTECTED],
[EMAIL PROTECTED], linux-kernel@vger.kernel.org,
[EMAIL PROTECTED], [EMAIL PROTECTED]
Re: [PATCH 0/2] LogFS take two
You seem to be missing the immutable bit. This is really useful
for dealing with buggy or badly-designed things running as root.
I've used to
Andrey Borzenkov writes:
This was posted in one of Russian forums. It was not possible to
archive (under Linux, using tar) vfat directory where files had
long Russian names (really long - over 150 - 170 characters) - tar
returned stat failure. When looking with plain ls, file names
appeared trun
1 - 100 of 417 matches
Mail list logo
