similar to: [PATCH] virtio-blk: free vblk-vqs in error path of virtblk_probe()

On Mon, Jun 15, 2020 at 12:14:59PM +0800, Hou Tao wrote: > Else there will be memory leak if alloc_disk() fails. > > Fixes: 6a27b656fc02 ("block: virtio-blk: support multi virt queues per virtio-blk device") > Signed-off-by: Hou Tao <houtao1 at huawei.com> > --- > drivers/block/virtio_blk.c | 1 + > 1 file changed, 1 insertion(+) > > diff --git

On 6/14/20 10:14 PM, Hou Tao wrote: > Else there will be memory leak if alloc_disk() fails. Applied, thanks. -- Jens Axboe

On Fri, Aug 04, 2023 at 09:03:20PM +0000, Verma, Vishal L wrote: > On Fri, 2023-08-04 at 20:39 +0200, Pankaj Gupta wrote: > > Gentle ping! > > > > Dan, Vishal for suggestion/review on this patch and request for merging. > > +Cc Michael for awareness, as virtio-pmem device is currently broken. > > Looks good to me, > > Reviewed-by: Vishal Verma

On Fri, Aug 04, 2023 at 09:03:20PM +0000, Verma, Vishal L wrote: > On Fri, 2023-08-04 at 20:39 +0200, Pankaj Gupta wrote: > > Gentle ping! > > > > Dan, Vishal for suggestion/review on this patch and request for merging. > > +Cc Michael for awareness, as virtio-pmem device is currently broken. > > Looks good to me, > > Reviewed-by: Vishal Verma

Based on a patch by Mark Wu <dwu at redhat.com> Current index allocation in virtio-blk is based on a monotonically increasing variable "index". This means we'll run out of numbers after a while. It also could cause confusion about the disk name in the case of hot-plugging disks. Change virtio-blk to use ida to allocate index, instead. Signed-off-by: Michael S. Tsirkin

Based on a patch by Mark Wu <dwu at redhat.com> Current index allocation in virtio-blk is based on a monotonically increasing variable "index". This means we'll run out of numbers after a while. It also could cause confusion about the disk name in the case of hot-plugging disks. Change virtio-blk to use ida to allocate index, instead. Signed-off-by: Michael S. Tsirkin

Current index allocation in virtio-blk is based on a monotonically increasing variable "index". It could cause some confusion about disk name in the case of hot-plugging disks. And it's impossible to find the lowest available index by just maintaining a simple index. So it's changed to use ida to allocate index via referring to the index allocation in scsi disk. Signed-off-by:

Current index allocation in virtio-blk is based on a monotonically increasing variable "index". It could cause some confusion about disk name in the case of hot-plugging disks. And it's impossible to find the lowest available index by just maintaining a simple index. So it's changed to use ida to allocate index via referring to the index allocation in scsi disk. Signed-off-by:

Hi, I hope someone can help point me in the right direction. I have a Sunfire x4100 running Solaris 10x86 06/06 with the Sun Studio 11 compiler. I am just trying to do a stock compile of dovecot-1.0.rc7 Ran the ./configure fine. See Below. Install prefix ...................... : /usr/local File offsets ........................ : 64bit I/O loop method ..................... : poll File change

Rusty, currently virtio_blk uses one major number per device. While this works quite well on most systems it is wasteful and will exhaust major numbers on larger installations. This patch allocates a major number on init and will use 16 minor numbers for each disk. That will allow ~64k virtio_blk disks. Signed-off-by: Christian Borntraeger <borntraeger@de.ibm.com> ---

Rusty, currently virtio_blk uses one major number per device. While this works quite well on most systems it is wasteful and will exhaust major numbers on larger installations. This patch allocates a major number on init and will use 16 minor numbers for each disk. That will allow ~64k virtio_blk disks. Signed-off-by: Christian Borntraeger <borntraeger@de.ibm.com> ---

On 28.04.23 11:50, Hou Wenlong wrote: > Similar to the alternative patching, use relative reference for original > instruction rather than absolute one, which saves 8 bytes for one entry > on x86_64. And it could generate R_X86_64_PC32 relocation instead of > R_X86_64_64 relocation, which also reduces relocation metadata on > relocatable builds. And the alignment could be hard

The latest upgrade of from samba 3.0.9 to samba 3.0.10 has caused problems on my samba server. On the Windows computers you can no longer see the WINS server ( the RedHat server) in the Network Neighborhood, say server1. The printers that we have added through the network neighborhood no longer work. One has to search for the full name of the server ( server1.xxx.xxx.edu) with the

----- Original Message ----- > From: "Xinliang David Li" <davidxl at google.com> > To: "Cong Hou" <congh at google.com> > Cc: "Hal Finkel" <hfinkel at anl.gov>, "llvm-dev" <llvm-dev at lists.llvm.org> > Sent: Wednesday, November 25, 2015 5:17:58 PM > Subject: Re: [llvm-dev] [RFC] Introducing a vector reduction add

I came across a problem when one of our clients was not able to access any of the servers on our network. This person has never connected to us before and now for this first time was trying to do it from his home is Houston, TX using earthlink cable service provided by Time Warner. All this information, I think, is important because when I started examining my shorewall logs I found out

Does anyone know of R functions for doing composite quantile regression (Hou and Yuan Ann Stat 36:1108, 2008)? The paper's authors do not talk about software in their paper or on their web sites. Thanks Frank ----- Frank Harrell Department of Biostatistics, Vanderbilt University -- View this message in context: http://r.789695.n4.nabble.com/Composite-Quantile-Regression-tp4663463.html

On Wed, Nov 25, 2015 at 2:32 PM, Hal Finkel <hfinkel at anl.gov> wrote: > Hi Cong, > > After reading the original RFC and this update, I'm still not entirely sure I understand the semantics of the flag you're proposing to add. Does it having something to do with the ordering of the reduction operations? The flag is only useful for vectorized reduction for now. I'll give

Help ! I am very happy with my 20001026 wine, running my favourites windows applications. Unfortunately, I still have a minor problem: My keyboard in perfectly recognized as the Brazilian ABNT layout, I had to change something in the keyboard.c file, but now is ok. So when I start my application I can get every character I need, but I can tell windows that a '~' followed by a

> >I suppose basically my question is: Is there anyway to get Windows to copy >the profile but exclude the 'My Documents' folder? Maybe you can find your answer at: http://www.windowsnetworking.com/kbase/WindowsTips/WindowsNT/RegistryTips/Disable/Disablecachingofroamingprofiles.html There hou can read: If you want roaming profiles to not include certain folders, you can

Having some issues with getting sound from a call. I have 4 systems. 3 main systems which handle calls for our 3 locations. The 4th system is the central voice mail system. When an inbound call gets passed to someones voice mail its done with an IAX2 connection. The same happens after hours when we have our night mode set. If you dial the main number after hours you are passed straight to the