Please respond urgently
Greetings, I am contacting you independently of my investigation and no one is informed of this communication. I need your urgent assistance in transferring the sum of $11.3million immediately to your private account.The money has been here in our Bank lying dormant for years now without anybody coming for the claim of it. I want to release the money to you as a relative to our deceased customer (the account owner) who died along with his supposed NEXT OF KIN on 16th October 2005. The Banking laws here do not allow such money to stay more than 17 years, because the money will be recalled to the Bank treasury account as unclaimed funds. By indicating your interest I will send you the full details on how the business will be executed. Please respond urgently and delete if you are not interested. Best Regards, Mr. Ahmed Hassan ___ devel mailing list de...@linuxdriverproject.org http://driverdev.linuxdriverproject.org/mailman/listinfo/driverdev-devel
Assist me purchase a living home
Assist me purchase a living home, .I have huge sum in financial institution .Should there be a need for an evidence, or a prove of my seriousness and genuineness. I have a Certificate of Deposit as a prove of fund. am from Syria, (where I can invest to sustain my living until the political crisis in my country is over).Could you please send me an email on ( ahmedhussein44...@gmail.com ) to enable me know you have received my email. Ahmed Hussein ___ devel mailing list de...@linuxdriverproject.org http://driverdev.linuxdriverproject.org/mailman/listinfo/driverdev-devel
Ahmed Al Qassim
Hello, Greetings to you my dear good friend, please my name is .Ahmed Al Qassim,a Bank Officer in one of the leading bank here in U.A.E. Please I have something very important and confidential [a business proposal] to discuss with you. Please kindly get back to me through my private contact E-mail Address so I can give you the details. E-mail : ahmedalqassi...@gmail.com Thanks, Ahmed Al Qassim ___ devel mailing list de...@linuxdriverproject.org http://driverdev.linuxdriverproject.org/mailman/listinfo/driverdev-devel
Hello,
Hello, I am Mr. Abdulahi Issa, from Burkina Faso in West African region. I work with the Bank of Africa here Which i am the audit manager . Can you safe Guard these amount( $13.5 Million USD) for me in your Country?? Further Details will be given to you if you show Interest. Regards Mr. Abdulahi Issa. ___ devel mailing list de...@linuxdriverproject.org http://driverdev.linuxdriverproject.org/mailman/listinfo/driverdev-devel
Re: RFC: staging: gasket: re-implement using UIO
Hi Todd, On Tue, Nov 06, 2018 at 04:20:49PM -0800, Todd Poynor wrote: > On Mon, Sep 10, 2018 at 8:28 AM Ahmed S. Darwish wrote: > > > > The gasket in-kernel framework, recently introduced under staging, > > re-implements what is already long-time provided by the UIO > > subsystem, with extra PCI BAR remapping and MSI conveniences. > > > > Before moving it out of staging, make sure we add the new bits to > > the UIO framework instead, then transform its signle client, the > > Apex driver, to a proper UIO driver (uio_driver.h). > > > > Link: https://lkml.kernel.org/r/20180828103817.GB1397@do-kernel > > So I'm looking at this for reals now. The BAR mapping stuff is > straightforward with the existing framework. Everything else could be > done outside of UIO via the existing device interface, but figured I'd > collect any opinions about adding the new bits to UIO. > If it won't slow you down, I'd actually be more than happy to get involved in adding the necessary bits to UIO. Thanks! -- Darwi http://darwish.chasingpointers.com ___ devel mailing list de...@linuxdriverproject.org http://driverdev.linuxdriverproject.org/mailman/listinfo/driverdev-devel
OK
Greetings, I have a business valued 15 million Euros. Kindly contact me for more explanation A. Zama +22675844869 ___ devel mailing list de...@linuxdriverproject.org http://driverdev.linuxdriverproject.org/mailman/listinfo/driverdev-devel
[PATCH] staging: gasket: TODO: re-implement using UIO
The gasket in-kernel framework, recently introduced under staging, re-implements what is already long-time provided by the UIO subsystem, with extra PCI BAR remapping and MSI conveniences. Before moving it out of staging, make sure we add the new bits to the UIO framework instead, then transform its signle client, the Apex driver, to a proper UIO driver (uio_driver.h). Link: https://lkml.kernel.org/r/20180828103817.GB1397@do-kernel Signed-off-by: Ahmed S. Darwish --- drivers/staging/gasket/TODO | 13 + 1 file changed, 13 insertions(+) diff --git a/drivers/staging/gasket/TODO b/drivers/staging/gasket/TODO index 6ff8e01b04cc..5b1865f8af2d 100644 --- a/drivers/staging/gasket/TODO +++ b/drivers/staging/gasket/TODO @@ -1,9 +1,22 @@ This is a list of things that need to be done to get this driver out of the staging directory. + +- Implement the gasket framework's functionality through UIO instead of + introducing a new user-space drivers framework that is quite similar. + + UIO provides the necessary bits to implement user-space drivers. Meanwhile + the gasket APIs adds some extra conveniences like PCI BAR mapping, and + MSI interrupts. Add these features to the UIO subsystem, then re-implement + the Apex driver as a basic UIO driver instead (include/linux/uio_driver.h) + - Document sysfs files with Documentation/ABI/ entries. + - Use misc interface instead of major number for driver version description. + - Add descriptions of module_param's + - apex_get_status() should actually check status. + - "drivers" should never be dealing with "raw" sysfs calls or mess around with kobjects at all. The driver core should handle all of this for you automaically. There should not be a need for raw attribute macros. -- Darwi http://darwish.chasingpointers.com ___ devel mailing list de...@linuxdriverproject.org http://driverdev.linuxdriverproject.org/mailman/listinfo/driverdev-devel
Re: [GIT PULL] Staging/IIO driver patches for 4.19-rc1
Hi!
On Tue, Aug 28, 2018 at 02:36:07PM +0200, Greg KH wrote:
> On Tue, Aug 28, 2018 at 10:38:17AM +0000, Ahmed S. Darwish wrote:
> > [ re-send; forgotten lkml CC added; sorry ]
> >
> > Hi,
> >
> > On Sat, 18 Aug 2018 17:57:24 +0200, Greg KH wrote:
> > [...]
> > > addition of some new IIO drivers. Also added was a "gasket" driver from
> > > Google that needs loads of work and the erofs filesystem.
> > >
> >
> > Why are we adding __a whole new in-kernel framework__ for
> > developing basic user-space drivers?
> >
> > We already have a frameowrk for that, and it's UIO. [1] The UIO
> > code is a very stable and simple subsystem; it's also heavily used
> > in the embedded industry..
>
> As Todd said, the code will end up being a simple UIO driver, if even
> that big, in th end. It is just going to take him a while to constantly
> refactor things until he achieves that goal...
>
> > I've looked at the gasket documentation [2], and the first user
> > of this new in-kernel API [3], and this is almost replicating UIO
> > it's not funny. [4] True, the gasket APIs adds some extra new
> > conveniences (PCI BAR re-mapping, MSI, ..), but there's no
> > technical reason this cannot be added to the UIO code instead.
>
> {shh} That's my plan :)
>
Cool, thanks a lot.
Can we then merge something like below patch?
[ I've searched the gasket included TODO file before posting,
but did not find any mention of UIO. Below patch will make
sure this will not be forgotten over time.. ]
==>
Subject: [PATCH] gasket: TODO: re-implement using UIO
The gasket in-kernel APIs, recently introduced under staging,
re-implements what is already long-time provided by the UIO
framework and subsystem.
Before moving it out of staging, make sure we add the new bits
to the UIO subsystem instead, then transform its signle client,
the Apex driver, to become a UIO driver (uio_driver.h)
Signed-off-by: Ahmed S. Darwish
---
drivers/staging/gasket/TODO | 13 +
1 file changed, 13 insertions(+)
diff --git a/drivers/staging/gasket/TODO b/drivers/staging/gasket/TODO
index 6ff8e01b04cc..5b1865f8af2d 100644
--- a/drivers/staging/gasket/TODO
+++ b/drivers/staging/gasket/TODO
@@ -1,9 +1,22 @@
This is a list of things that need to be done to get this driver out of the
staging directory.
+
+- Implement the gasket framework's functionality through UIO instead of
+ introducing a new user-space drivers framework that is quite similar.
+
+ UIO provides the necessary bits to implement user-space drivers. Meanwhile
+ the gasket APIs adds some extra conveniences like PCI BAR mapping, and
+ MSI interrupts. Add these features to the UIO subsystem, then re-implement
+ the Apex driver as a basic UIO driver instead (include/linux/uio_driver.h)
+
- Document sysfs files with Documentation/ABI/ entries.
+
- Use misc interface instead of major number for driver version description.
+
- Add descriptions of module_param's
+
- apex_get_status() should actually check status.
+
- "drivers" should never be dealing with "raw" sysfs calls or mess around with
kobjects at all. The driver core should handle all of this for you
automaically. There should not be a need for raw attribute macros.
Ciao,
--
Darwish
http://darwish.chasingpointers.com
___
devel mailing list
de...@linuxdriverproject.org
http://driverdev.linuxdriverproject.org/mailman/listinfo/driverdev-devel
Re: [GIT PULL] Staging/IIO driver patches for 4.19-rc1
[ re-send; forgotten lkml CC added; sorry ] Hi, On Sat, 18 Aug 2018 17:57:24 +0200, Greg KH wrote: [...] > addition of some new IIO drivers. Also added was a "gasket" driver from > Google that needs loads of work and the erofs filesystem. > Why are we adding __a whole new in-kernel framework__ for developing basic user-space drivers? We already have a frameowrk for that, and it's UIO. [1] The UIO code is a very stable and simple subsystem; it's also heavily used in the embedded industry.. I've looked at the gasket documentation [2], and the first user of this new in-kernel API [3], and this is almost replicating UIO it's not funny. [4] True, the gasket APIs adds some extra new conveniences (PCI BAR re-mapping, MSI, ..), but there's no technical reason this cannot be added to the UIO code instead. More-over, the exposed user-space API is just some ioctls. So if google hase some shipped user-space code that is using this, hopefully the driver can still be re-implemented through UIO without changing these bits.. Thanks, [1] https://www.kernel.org/doc/html/v4.18/driver-api/uio-howto.html [2] drivers/staging/gasket/gasket_core.h :: struct gasket_driver_desc [3] drivers/staging/gasket/apex_driver.c [4] include/linux/uio_driver.h -- Darwi http://darwish.chasingpointers.com ___ devel mailing list de...@linuxdriverproject.org http://driverdev.linuxdriverproject.org/mailman/listinfo/driverdev-devel
OK
Dear Friend, I have a profitable business to share with you .But only need your permision to disclose it to you. Thanks Ahmed Zama ___ devel mailing list de...@linuxdriverproject.org http://driverdev.linuxdriverproject.org/mailman/listinfo/driverdev-devel
OK
Greetings, Are you capable to handle a profitable transaction valued 15 million Euros?Reply me for more information Ahmed Zama ___ devel mailing list de...@linuxdriverproject.org http://driverdev.linuxdriverproject.org/mailman/listinfo/driverdev-devel
[PATCH] X86/UAPI: Use __u64 instead of u64 in hyperv.h
... since u64 has a hidden header dependency that was not there before
using it (i.e. it breaks our VMM build). Also, __u64 is the right way to
expose the data type through UAPI.
Fixes: 93286261 ("x86/hyperv: Reenlightenment notifications support")
Signed-off-by: KarimAllah Ahmed <karah...@amazon.de>
Cc: K. Y. Srinivasan <k...@microsoft.com>
Cc: Haiyang Zhang <haiya...@microsoft.com>
Cc: Stephen Hemminger <sthem...@microsoft.com>
Cc: Thomas Gleixner <t...@linutronix.de>
Cc: Ingo Molnar <mi...@redhat.com>
Cc: H. Peter Anvin <h...@zytor.com>
Cc: x...@kernel.org
Cc: de...@linuxdriverproject.org
Cc: linux-ker...@vger.kernel.org
---
arch/x86/include/uapi/asm/hyperv.h | 18 +-
1 file changed, 9 insertions(+), 9 deletions(-)
diff --git a/arch/x86/include/uapi/asm/hyperv.h
b/arch/x86/include/uapi/asm/hyperv.h
index 197c2e6..0994143 100644
--- a/arch/x86/include/uapi/asm/hyperv.h
+++ b/arch/x86/include/uapi/asm/hyperv.h
@@ -241,24 +241,24 @@
#define HV_X64_MSR_REENLIGHTENMENT_CONTROL 0x4106
struct hv_reenlightenment_control {
- u64 vector:8;
- u64 reserved1:8;
- u64 enabled:1;
- u64 reserved2:15;
- u64 target_vp:32;
+ __u64 vector:8;
+ __u64 reserved1:8;
+ __u64 enabled:1;
+ __u64 reserved2:15;
+ __u64 target_vp:32;
};
#define HV_X64_MSR_TSC_EMULATION_CONTROL 0x4107
#define HV_X64_MSR_TSC_EMULATION_STATUS0x4108
struct hv_tsc_emulation_control {
- u64 enabled:1;
- u64 reserved:63;
+ __u64 enabled:1;
+ __u64 reserved:63;
};
struct hv_tsc_emulation_status {
- u64 inprogress:1;
- u64 reserved:63;
+ __u64 inprogress:1;
+ __u64 reserved:63;
};
#define HV_X64_MSR_HYPERCALL_ENABLE0x0001
--
2.7.4
___
devel mailing list
de...@linuxdriverproject.org
http://driverdev.linuxdriverproject.org/mailman/listinfo/driverdev-devel
I need your cooperation
Dear Friend, I know that this mail will come to you as a surprise as we have never met before, but need not to worry as I am contacting you independently of my investigation and no one is informed of this communication. I need your urgent assistance in transferring the sum of $11.3million immediately to your private account.The money has been here in our Bank lying dormant for years now without anybody coming for the claim of it. I want to release the money to you as the relative to our deceased customer (the account owner) who died a long with his supposed NEXT OF KIN since 16th October 2005. The Banking laws here does not allow such money to stay more than 12 years, because the money will be recalled to the Bank treasury account as unclaimed fund. By indicating your interest I will send you the full details on how the business will be executed. Please respond urgently and delete if you are not interested. Best Regards, Mr. Ahmed Hassan. ___ devel mailing list de...@linuxdriverproject.org http://driverdev.linuxdriverproject.org/mailman/listinfo/driverdev-devel
Re: Possible memory leak in function (reserve_range) not freeing pointer (regionid)
The bug was found via the memory-leak static analysis tool that we have built on top of C-Atlas framework from EnSoft. You can check it out (http://www.ensoftcorp.com/atlas/). Thanks for clarifying things! ~Ahmed On Wed, Dec 3, 2014 at 2:48 AM, Dan Carpenter dan.carpen...@oracle.com wrote: This is a real bug, but it's very minor. To trigger it, you would have to modprobe and rmmod many many times in a loop. If you report these sorts of minor bugs when the code is new, then most times people fix them but this one is old I doubt anyone is motivated to fix it. Fixing it seems a little complicated to me as well. I suppose that linux-ker...@vger.kernel.org is the correct mailing list to report this but the truth is that no one reads that list. Anyway, it seems that you have written a good bug finding tool. :) Congratulations for that! regards, dan carpenter ___ devel mailing list de...@linuxdriverproject.org http://driverdev.linuxdriverproject.org/mailman/listinfo/driverdev-devel
Possible memory leak in function (reserve_range) not freeing pointer (regionid)
Bug Report: https://bugzilla.kernel.org/show_bug.cgi?id=89101 Linux Version [3.17-rc1] Configuration: Default configuration for x86 Function (reserve_range) in file (drivers/pnp/system.c) allocates pointer (regionid) on line (32) and passes it to function (__request_region) through the macros: (request_region) at line (38) or (request_mem_region) at line (40). However, if the resource (res) is allocated through (__request_region) function, then the pointer (res-name) points to the allocated pointer (regionid). Then, there is no way in function (free_resource) or function (release_resource) to free the pointer (regionid) or (res-name). Thus, causing a potential memory leak! Function (reserve_range) source code reference: http://lxr.free-electrons.com/source/drivers/pnp/system.c#L25 Function (free_resource) source code reference:http://lxr.free-electrons.com/source/kernel/resource.c#L172 Function (release_resource) source code reference:http://lxr.free-electrons.com/source/kernel/resource.c#L322 ~Ahmed ___ devel mailing list de...@linuxdriverproject.org http://driverdev.linuxdriverproject.org/mailman/listinfo/driverdev-devel
Re: Possible memory leak in function (reserve_range) not freeing pointer (regionid)
On Sun, Nov 30, 2014 at 8:51 PM, Greg KH gre...@linuxfoundation.org wrote: On Sun, Nov 30, 2014 at 02:00:45PM -0600, Ahmed Tamrawi wrote: Bug Report: https://bugzilla.kernel.org/show_bug.cgi?id=89101 Linux Version [3.17-rc1] That's a very old kernel version. It does exist on the latest version (v3.18-rc7) Configuration: Default configuration for x86 Function (reserve_range) in file (drivers/pnp/system.c) allocates pointer (regionid) on line (32) and passes it to function (__request_region) through the macros: (request_region) at line (38) or (request_mem_region) at line (40). However, if the resource (res) is allocated through (__request_region) function, then the pointer (res-name) points to the allocated pointer (regionid). Then, there is no way in function (free_resource) or function (release_resource) to free the pointer (regionid) or (res-name). Thus, causing a potential memory leak! How does this relate to the mailing list you sent this to? The bug occurs in the drivers side code in pnp/system.c. I thought this is the list to target. I have already posted the bug into linux-kernel mailing list, does that suffice? Please send a patch for the issue against Linus's latest kernel tree to help explain things better. I am not sure where the fix should be, but I can try one. thanks, greg k-h ___ devel mailing list de...@linuxdriverproject.org http://driverdev.linuxdriverproject.org/mailman/listinfo/driverdev-devel
URGENT BUSINESS REQUEST
Dear Friend I am Mr. Ahmed Zama,I work for UBA bank Ouagadougou Burkina Faso. I have a business proposal which concerns the transfer of 4.8 M Euros into a foreign account. Everything about this transaction shall be legally done without any problem. If you are interested to help me, I will give you more details as soon as I receive your positive response. You will be entitled to 30%, 60% will be for me, While 10% will be mapped out for expenses that may be incurred on the process of transferring this fund. If you are willing to work with me, send me immediately the information listed bellow. Name .. Nationality .. Age.. Occupation .. Mobile Telephone Line.. Address Thanks Ahmed Zama --- Ce courrier électronique ne contient aucun virus ou logiciel malveillant parce que la protection avast! Antivirus est active. http://www.avast.com ___ devel mailing list de...@linuxdriverproject.org http://driverdev.linuxdriverproject.org/mailman/listinfo/driverdev-devel
