Displaying 20 results from an estimated 3000 matches similar to: "Btrfs v0.14 Released"
2008 Feb 06
1
[PATCH 1/4] btrfs: Add workaround for AppArmor changing remove_suid() prototype
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
In openSUSE 10.3, AppArmor modifies remove_suid to take a struct path
rather than just a dentry. This patch tests that the kernel is openSUSE
10.3 or newer and adjusts the call accordingly.
Debian/Ubuntu with AppArmor applied will also need a similar patch.
Maintainers of btrfs under those distributions should build on this
patch or,
2008 Jul 03
2
iozone remove_suid oops...
Having done a current checkout, creating a new FS and running iozone
[1] on it results in an oops [2]. remove_suid is called, accessing
offset 14 of a NULL pointer.
Let me know if you''d like me to test any fix, do further debugging or
get more information.
Thanks,
Daniel
--- [1]
# mkfs.btrfs /dev/sda4
# mount /dev/sda4 /mnt
/mnt# iozone -a .
--- [2]
[ 899.118926] BUG: unable to
2009 Jul 06
2
[Patch v2] btrfs: use file_remove_suid() after i_mutex is held
V1 -> V2:
Move kmalloc() before mutex_lock(), suggested by Arjan.
file_remove_suid() should be called with i_mutex held,
file_update_time() too. So move them after mutex_lock().
Plus, check the return value of kmalloc().
Signed-off-by: WANG Cong <amwang@redhat.com>
Cc: Arjan <arjan@infradead.org>
Cc: Chris Mason <chris.mason@oracle.com>
Cc: Yan Zheng
2009 Jul 06
1
[Patch v3] btrfs: use file_remove_suid() after i_mutex is held
V2 -> V3:
set ''err'' to -ENOMEM when kmalloc() fails. Thanks to Tao.
V1 -> V2:
Move kmalloc() before mutex_lock(), suggested by Arjan.
file_remove_suid() should be called with i_mutex held,
file_update_time() too. So move them after mutex_lock().
Plus, check the return value of kmalloc().
Signed-off-by: WANG Cong <amwang@redhat.com>
Cc: Arjan
2008 Jan 19
1
[bugreport] btrfs 0.11
Hi,
uname -a: Linux btrfstest 2.6.24-4-generic #1 SMP Mon Jan 14 17:30:39
UTC 2008 i686 GNU/Linux
btrfs version: 0.11
fs: /dev/sda5 on /mnt type btrfs (rw)
root@btrfstest:/tmp# dd if=/dev/zero of=foobar bs=1024 count=100000
100000+0 records in
100000+0 records out
102400000 bytes (102 MB) copied, 15.5326 seconds, 6.6 MB/s
root@btrfstest:/tmp# cp foobar /mnt/
Segmentation fault
2009 Jul 06
2
[Patch] btrfs: use file_remove_suid() after i_mutex is held
file_remove_suid() should be called with i_mutex held,
file_update_time() too. So move them after mutex_lock().
Plus, check the return value of kmalloc().
Signed-off-by: WANG Cong <amwang@redhat.com>
---
diff --git a/fs/btrfs/file.c b/fs/btrfs/file.c
index 7c3cd24..cd36301 100644
--- a/fs/btrfs/file.c
+++ b/fs/btrfs/file.c
@@ -944,14 +944,17 @@ static ssize_t btrfs_file_write(struct file
2016 Apr 04
2
[PATCH] virtio: fix "warning: ‘queue’ may be used uninitialized"
This fixes the following warning:
drivers/virtio/virtio_ring.c:1032:5: warning: ?queue? may be used
uninitialized in this function
The conditions that govern when queue is set aren't apparent to gcc.
Setting queue = NULL clears the warning.
Signed-off-by: Jeff Mahoney <jeffm at suse.com>
---
drivers/virtio/virtio_ring.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
---
2016 Apr 04
2
[PATCH] virtio: fix "warning: ‘queue’ may be used uninitialized"
This fixes the following warning:
drivers/virtio/virtio_ring.c:1032:5: warning: ?queue? may be used
uninitialized in this function
The conditions that govern when queue is set aren't apparent to gcc.
Setting queue = NULL clears the warning.
Signed-off-by: Jeff Mahoney <jeffm at suse.com>
---
drivers/virtio/virtio_ring.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
---
2016 Apr 05
1
Re: [PATCH] virtio: fix "warning: ‘queue’ may be used uninitialized"
On 4/5/16 4:04 AM, Michael S. Tsirkin wrote:
> On Mon, Apr 04, 2016 at 02:14:19PM -0400, Jeff Mahoney wrote:
>> This fixes the following warning:
>> drivers/virtio/virtio_ring.c:1032:5: warning: ?queue? may be used
>> uninitialized in this function
>>
>> The conditions that govern when queue is set aren't apparent to gcc.
>>
>> Setting queue = NULL
2016 Apr 05
1
Re: [PATCH] virtio: fix "warning: ‘queue’ may be used uninitialized"
On 4/5/16 4:04 AM, Michael S. Tsirkin wrote:
> On Mon, Apr 04, 2016 at 02:14:19PM -0400, Jeff Mahoney wrote:
>> This fixes the following warning:
>> drivers/virtio/virtio_ring.c:1032:5: warning: ?queue? may be used
>> uninitialized in this function
>>
>> The conditions that govern when queue is set aren't apparent to gcc.
>>
>> Setting queue = NULL
2009 Oct 08
1
Drop Call on ICMP Port Unreachable?
One of our users recently had a powerfail while connected to our meetme
gateway. (Asterisk 1.4.17 on debian 4.0)
Through the course of it, asterisk never hung up. His system came back
up, and started sending ICMP port unreachables, but the stream went on,
flooding him with "silence" media stream packets (there was nobody else in
the conference).
Is asterisk aware of ICMP
2007 Oct 10
2
Homedir Access without exposing whole Homedir.
Hello All,
Dovecot 1.0.3
I am coming from UW IMAP, and I'm finding for some reason that mail is
getting stored in a variety of places (which I believe, is because by
default UW imap allowed access to the entire home directory).
All files are mbox. My default delivery location is ~/.mail
Thus:
* At least a couple of my users have mail in ~/INBOX, as well as
~/INBOX.drafts (not many
2004 Sep 01
1
Odd PRI Behavior
When using a PRI, after the remote party hangs up, asterisk tries to spawn
a call to the "h" extension. Is this normal behavior for a pri to try to
call the "h" extension to try to clean things up?
Call Comes In:
-- Executing Dial("Zap/1-1", "SIP/16464436000@AST-237.65") in new stack
-- Called 16464436000@AST-237.65
-- Accepting call from
2004 Aug 10
2
SNOM 200 and Asterisk Woes
Okay, this one is driving me nuts.
I have a fedora core 1 machine running asterisk from CVS. Built last
week. I have a couple of snom phones with the latest firmware.
Here's the issue, it's a wierd one.
You start up the phones, they register, all is good. They show up in sip
show peers like thus:
danm/danm 65.125.237.91 D N 255.255.255.255 5060 OK
(29 ms)
2011 Oct 04
68
[patch 00/65] Error handling patchset v3
Hi all -
Here''s my current error handling patchset, against 3.1-rc8. Almost all of
this patchset is preparing for actual error handling. Before we start in
on that work, I''m trying to reduce the surface we need to worry about. It
turns out that there is a ton of code that returns an error code but never
actually reports an error.
The patchset has grown to 65 patches. 46 of them
2004 Aug 17
1
BroadVOX
Guys,
For what it's worth, after months of trying to troubleshoot issues with
them, and after paying them around $2500 for setup and a down payment
(it's unclear what of that will be refunded, if any) BroadVox --
http://www.broadvox.net/ -- decided to terminate our contract without any
valid reason, and the only explanation they could cite was "it's because
of the software
2007 Apr 10
1
Several clusters in the same matchine
Hi,
is it possible to have several ocfs2 clusters in the same machine?
We have webserver1 and webserver2 that should belong to cluster1 and
cluster2 "workgroup".
Cluster1 should be made of webserver1, webserver2 and application_server1
Cluster2 should be made of webserver1, webserver2 and application_server2
Is this possible?
Thanks,
Nuno Fernandes
2008 Jan 17
3
tool that records and plots graphs of UPS load over time?
Hi
I'm looking for a tool that records and plots graphs of UPS load over
time?
Any suggestions?
JonB
2020 Apr 16
2
suggestion: "." in [lsv]apply()
I'm sure this exists elsewhere, but, as a trade-off, could you achieve
what you want with a separate helper function F(expr) that constructs
the function you want to pass to [lsv]apply()? Something that would
allow you to write:
sapply(split(mtcars, mtcars$cyl), F(summary(lm(mpg ~ wt,.))$r.squared))
Such an F() function would apply elsewhere too.
/Henrik
On Thu, Apr 16, 2020 at 9:30 AM
2017 Dec 29
5
Legacy option for key length?
All,
I occasionally manage some APC PDU devices. I manage them via a VPN,
which enforces super-heavy crypto, and their access is restricted to only
jumphosts and the VPN. Basically, the only time you need to log into
these is when you go to reboot something that's down.
Their web UI with SSL doesn't work with modern browsers.
Their CPU is...tiny, and their SSHd implementation