2010-01-30 23:26:47 +01:00
|
|
|
/*
|
2013-07-12 22:11:08 +02:00
|
|
|
* Original author: M. Tourne
|
|
|
|
*
|
2015-04-13 09:36:54 +02:00
|
|
|
* This file is part of mpv.
|
|
|
|
*
|
|
|
|
* mpv is free software; you can redistribute it and/or modify
|
2010-01-30 23:26:47 +01:00
|
|
|
* it under the terms of the GNU General Public License as published by
|
|
|
|
* the Free Software Foundation; either version 2 of the License, or
|
|
|
|
* (at your option) any later version.
|
|
|
|
*
|
2015-04-13 09:36:54 +02:00
|
|
|
* mpv is distributed in the hope that it will be useful,
|
2010-01-30 23:26:47 +01:00
|
|
|
* but WITHOUT ANY WARRANTY; without even the implied warranty of
|
|
|
|
* MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
|
|
|
|
* GNU General Public License for more details.
|
|
|
|
*
|
|
|
|
* You should have received a copy of the GNU General Public License along
|
2015-04-13 09:36:54 +02:00
|
|
|
* with mpv. If not, see <http://www.gnu.org/licenses/>.
|
2010-01-30 23:26:47 +01:00
|
|
|
*/
|
2005-05-19 22:58:11 +02:00
|
|
|
|
|
|
|
#include "config.h"
|
|
|
|
|
|
|
|
#include <libsmbclient.h>
|
|
|
|
#include <unistd.h>
|
|
|
|
|
2013-12-17 02:39:45 +01:00
|
|
|
#include "common/msg.h"
|
2005-05-19 22:58:11 +02:00
|
|
|
#include "stream.h"
|
2013-12-17 02:02:25 +01:00
|
|
|
#include "options/m_option.h"
|
2005-05-19 22:58:11 +02:00
|
|
|
|
stream: remove fd member
Stream implementations could set this to a unix file descriptor. The
generic stream code could use it as fallback for a few things. This
was confusing and insane. In most cases, the stream implementations
defined all callbacks, so setting the fd member didn't have any
advantages, other than avoiding defining a private struct to store it.
It appears that even if the stream implementation used close() on the
fd (or something equivalent), stream.c would close() it a second time
(and on windows, even would call closesocket()), which should be proof
for the insanity of this code.
For stream_file.c, additionally make sure we don't close stdin or
stdout if "-" is used as filename.
For stream_vcd.c, remove the control() code. This code most likely
didn't make the slightest sense, because it used a different type
for stream->priv. It also leaked memory. Maybe it worked, but it's
incorrect and insignificant anyway, so kill it. This code was added
with commit 9521c19 (svn commit 31019).
Untested for all protocols other than stream_file.c.
2013-07-12 22:07:07 +02:00
|
|
|
struct priv {
|
|
|
|
int fd;
|
|
|
|
};
|
|
|
|
|
2005-05-19 22:58:11 +02:00
|
|
|
static void smb_auth_fn(const char *server, const char *share,
|
|
|
|
char *workgroup, int wgmaxlen, char *username, int unmaxlen,
|
2014-04-13 18:00:51 +02:00
|
|
|
char *password, int pwmaxlen)
|
2005-05-19 22:58:11 +02:00
|
|
|
{
|
2013-12-22 23:42:58 +01:00
|
|
|
strncpy(workgroup, "LAN", wgmaxlen - 1);
|
2005-05-19 22:58:11 +02:00
|
|
|
}
|
|
|
|
|
2006-12-19 23:31:10 +01:00
|
|
|
static int control(stream_t *s, int cmd, void *arg) {
|
stream: remove fd member
Stream implementations could set this to a unix file descriptor. The
generic stream code could use it as fallback for a few things. This
was confusing and insane. In most cases, the stream implementations
defined all callbacks, so setting the fd member didn't have any
advantages, other than avoiding defining a private struct to store it.
It appears that even if the stream implementation used close() on the
fd (or something equivalent), stream.c would close() it a second time
(and on windows, even would call closesocket()), which should be proof
for the insanity of this code.
For stream_file.c, additionally make sure we don't close stdin or
stdout if "-" is used as filename.
For stream_vcd.c, remove the control() code. This code most likely
didn't make the slightest sense, because it used a different type
for stream->priv. It also leaked memory. Maybe it worked, but it's
incorrect and insignificant anyway, so kill it. This code was added
with commit 9521c19 (svn commit 31019).
Untested for all protocols other than stream_file.c.
2013-07-12 22:07:07 +02:00
|
|
|
struct priv *p = s->priv;
|
2006-12-19 23:31:10 +01:00
|
|
|
switch(cmd) {
|
|
|
|
case STREAM_CTRL_GET_SIZE: {
|
stream: remove fd member
Stream implementations could set this to a unix file descriptor. The
generic stream code could use it as fallback for a few things. This
was confusing and insane. In most cases, the stream implementations
defined all callbacks, so setting the fd member didn't have any
advantages, other than avoiding defining a private struct to store it.
It appears that even if the stream implementation used close() on the
fd (or something equivalent), stream.c would close() it a second time
(and on windows, even would call closesocket()), which should be proof
for the insanity of this code.
For stream_file.c, additionally make sure we don't close stdin or
stdout if "-" is used as filename.
For stream_vcd.c, remove the control() code. This code most likely
didn't make the slightest sense, because it used a different type
for stream->priv. It also leaked memory. Maybe it worked, but it's
incorrect and insignificant anyway, so kill it. This code was added
with commit 9521c19 (svn commit 31019).
Untested for all protocols other than stream_file.c.
2013-07-12 22:07:07 +02:00
|
|
|
off_t size = smbc_lseek(p->fd,0,SEEK_END);
|
|
|
|
smbc_lseek(p->fd,s->pos,SEEK_SET);
|
2006-12-19 23:31:10 +01:00
|
|
|
if(size != (off_t)-1) {
|
2014-05-24 14:04:09 +02:00
|
|
|
*(int64_t *)arg = size;
|
2006-12-19 23:31:10 +01:00
|
|
|
return 1;
|
|
|
|
}
|
|
|
|
}
|
2014-05-24 14:04:09 +02:00
|
|
|
break;
|
2006-12-19 23:31:10 +01:00
|
|
|
}
|
2007-08-29 00:38:45 +02:00
|
|
|
return STREAM_UNSUPPORTED;
|
2006-12-19 23:31:10 +01:00
|
|
|
}
|
|
|
|
|
2012-11-18 20:46:12 +01:00
|
|
|
static int seek(stream_t *s,int64_t newpos) {
|
stream: remove fd member
Stream implementations could set this to a unix file descriptor. The
generic stream code could use it as fallback for a few things. This
was confusing and insane. In most cases, the stream implementations
defined all callbacks, so setting the fd member didn't have any
advantages, other than avoiding defining a private struct to store it.
It appears that even if the stream implementation used close() on the
fd (or something equivalent), stream.c would close() it a second time
(and on windows, even would call closesocket()), which should be proof
for the insanity of this code.
For stream_file.c, additionally make sure we don't close stdin or
stdout if "-" is used as filename.
For stream_vcd.c, remove the control() code. This code most likely
didn't make the slightest sense, because it used a different type
for stream->priv. It also leaked memory. Maybe it worked, but it's
incorrect and insignificant anyway, so kill it. This code was added
with commit 9521c19 (svn commit 31019).
Untested for all protocols other than stream_file.c.
2013-07-12 22:07:07 +02:00
|
|
|
struct priv *p = s->priv;
|
2013-08-22 18:23:33 +02:00
|
|
|
if(smbc_lseek(p->fd,newpos,SEEK_SET)<0) {
|
2005-05-19 22:58:11 +02:00
|
|
|
return 0;
|
|
|
|
}
|
|
|
|
return 1;
|
|
|
|
}
|
|
|
|
|
|
|
|
static int fill_buffer(stream_t *s, char* buffer, int max_len){
|
stream: remove fd member
Stream implementations could set this to a unix file descriptor. The
generic stream code could use it as fallback for a few things. This
was confusing and insane. In most cases, the stream implementations
defined all callbacks, so setting the fd member didn't have any
advantages, other than avoiding defining a private struct to store it.
It appears that even if the stream implementation used close() on the
fd (or something equivalent), stream.c would close() it a second time
(and on windows, even would call closesocket()), which should be proof
for the insanity of this code.
For stream_file.c, additionally make sure we don't close stdin or
stdout if "-" is used as filename.
For stream_vcd.c, remove the control() code. This code most likely
didn't make the slightest sense, because it used a different type
for stream->priv. It also leaked memory. Maybe it worked, but it's
incorrect and insignificant anyway, so kill it. This code was added
with commit 9521c19 (svn commit 31019).
Untested for all protocols other than stream_file.c.
2013-07-12 22:07:07 +02:00
|
|
|
struct priv *p = s->priv;
|
|
|
|
int r = smbc_read(p->fd,buffer,max_len);
|
2005-05-19 22:58:11 +02:00
|
|
|
return (r <= 0) ? -1 : r;
|
|
|
|
}
|
|
|
|
|
|
|
|
static int write_buffer(stream_t *s, char* buffer, int len) {
|
stream: remove fd member
Stream implementations could set this to a unix file descriptor. The
generic stream code could use it as fallback for a few things. This
was confusing and insane. In most cases, the stream implementations
defined all callbacks, so setting the fd member didn't have any
advantages, other than avoiding defining a private struct to store it.
It appears that even if the stream implementation used close() on the
fd (or something equivalent), stream.c would close() it a second time
(and on windows, even would call closesocket()), which should be proof
for the insanity of this code.
For stream_file.c, additionally make sure we don't close stdin or
stdout if "-" is used as filename.
For stream_vcd.c, remove the control() code. This code most likely
didn't make the slightest sense, because it used a different type
for stream->priv. It also leaked memory. Maybe it worked, but it's
incorrect and insignificant anyway, so kill it. This code was added
with commit 9521c19 (svn commit 31019).
Untested for all protocols other than stream_file.c.
2013-07-12 22:07:07 +02:00
|
|
|
struct priv *p = s->priv;
|
2011-02-10 22:25:38 +01:00
|
|
|
int r;
|
|
|
|
int wr = 0;
|
|
|
|
while (wr < len) {
|
stream: remove fd member
Stream implementations could set this to a unix file descriptor. The
generic stream code could use it as fallback for a few things. This
was confusing and insane. In most cases, the stream implementations
defined all callbacks, so setting the fd member didn't have any
advantages, other than avoiding defining a private struct to store it.
It appears that even if the stream implementation used close() on the
fd (or something equivalent), stream.c would close() it a second time
(and on windows, even would call closesocket()), which should be proof
for the insanity of this code.
For stream_file.c, additionally make sure we don't close stdin or
stdout if "-" is used as filename.
For stream_vcd.c, remove the control() code. This code most likely
didn't make the slightest sense, because it used a different type
for stream->priv. It also leaked memory. Maybe it worked, but it's
incorrect and insignificant anyway, so kill it. This code was added
with commit 9521c19 (svn commit 31019).
Untested for all protocols other than stream_file.c.
2013-07-12 22:07:07 +02:00
|
|
|
r = smbc_write(p->fd,buffer,len);
|
2011-02-10 22:25:38 +01:00
|
|
|
if (r <= 0)
|
|
|
|
return -1;
|
|
|
|
wr += r;
|
|
|
|
buffer += r;
|
|
|
|
}
|
|
|
|
return len;
|
2005-05-19 22:58:11 +02:00
|
|
|
}
|
|
|
|
|
|
|
|
static void close_f(stream_t *s){
|
stream: remove fd member
Stream implementations could set this to a unix file descriptor. The
generic stream code could use it as fallback for a few things. This
was confusing and insane. In most cases, the stream implementations
defined all callbacks, so setting the fd member didn't have any
advantages, other than avoiding defining a private struct to store it.
It appears that even if the stream implementation used close() on the
fd (or something equivalent), stream.c would close() it a second time
(and on windows, even would call closesocket()), which should be proof
for the insanity of this code.
For stream_file.c, additionally make sure we don't close stdin or
stdout if "-" is used as filename.
For stream_vcd.c, remove the control() code. This code most likely
didn't make the slightest sense, because it used a different type
for stream->priv. It also leaked memory. Maybe it worked, but it's
incorrect and insignificant anyway, so kill it. This code was added
with commit 9521c19 (svn commit 31019).
Untested for all protocols other than stream_file.c.
2013-07-12 22:07:07 +02:00
|
|
|
struct priv *p = s->priv;
|
|
|
|
smbc_close(p->fd);
|
2005-05-19 22:58:11 +02:00
|
|
|
}
|
|
|
|
|
2014-05-24 14:06:13 +02:00
|
|
|
static int open_f (stream_t *stream)
|
2013-07-11 21:10:42 +02:00
|
|
|
{
|
2005-05-19 22:58:11 +02:00
|
|
|
char *filename;
|
2012-11-18 20:46:12 +01:00
|
|
|
int64_t len;
|
2005-05-19 22:58:11 +02:00
|
|
|
int fd, err;
|
2009-07-07 01:26:13 +02:00
|
|
|
|
stream: remove fd member
Stream implementations could set this to a unix file descriptor. The
generic stream code could use it as fallback for a few things. This
was confusing and insane. In most cases, the stream implementations
defined all callbacks, so setting the fd member didn't have any
advantages, other than avoiding defining a private struct to store it.
It appears that even if the stream implementation used close() on the
fd (or something equivalent), stream.c would close() it a second time
(and on windows, even would call closesocket()), which should be proof
for the insanity of this code.
For stream_file.c, additionally make sure we don't close stdin or
stdout if "-" is used as filename.
For stream_vcd.c, remove the control() code. This code most likely
didn't make the slightest sense, because it used a different type
for stream->priv. It also leaked memory. Maybe it worked, but it's
incorrect and insignificant anyway, so kill it. This code was added
with commit 9521c19 (svn commit 31019).
Untested for all protocols other than stream_file.c.
2013-07-12 22:07:07 +02:00
|
|
|
struct priv *priv = talloc_zero(stream, struct priv);
|
|
|
|
stream->priv = priv;
|
|
|
|
|
2005-05-19 22:58:11 +02:00
|
|
|
filename = stream->url;
|
2009-07-07 01:26:13 +02:00
|
|
|
|
2014-05-24 17:00:30 +02:00
|
|
|
bool write = stream->mode == STREAM_WRITE;
|
|
|
|
mode_t m = write ? O_RDWR|O_CREAT|O_TRUNC : O_RDONLY;
|
2009-07-07 01:26:13 +02:00
|
|
|
|
2005-05-19 22:58:11 +02:00
|
|
|
if(!filename) {
|
2013-12-21 20:36:45 +01:00
|
|
|
MP_ERR(stream, "[smb] Bad url\n");
|
2005-05-19 22:58:11 +02:00
|
|
|
return STREAM_ERROR;
|
|
|
|
}
|
2009-07-07 01:26:13 +02:00
|
|
|
|
2005-05-19 22:58:11 +02:00
|
|
|
err = smbc_init(smb_auth_fn, 1);
|
|
|
|
if (err < 0) {
|
2013-12-21 20:36:45 +01:00
|
|
|
MP_ERR(stream, "Cannot init the libsmbclient library: %d\n",err);
|
2005-05-19 22:58:11 +02:00
|
|
|
return STREAM_ERROR;
|
|
|
|
}
|
2009-07-07 01:26:13 +02:00
|
|
|
|
2005-05-19 22:58:11 +02:00
|
|
|
fd = smbc_open(filename, m,0644);
|
2009-07-07 01:26:13 +02:00
|
|
|
if (fd < 0) {
|
2013-12-21 20:36:45 +01:00
|
|
|
MP_ERR(stream, "Could not open from LAN: '%s'\n", filename);
|
2005-05-19 22:58:11 +02:00
|
|
|
return STREAM_ERROR;
|
|
|
|
}
|
2009-07-07 01:26:13 +02:00
|
|
|
|
2006-12-19 23:31:10 +01:00
|
|
|
len = 0;
|
2014-05-24 17:00:30 +02:00
|
|
|
if(!write) {
|
2006-12-20 21:30:08 +01:00
|
|
|
len = smbc_lseek(fd,0,SEEK_END);
|
|
|
|
smbc_lseek (fd, 0, SEEK_SET);
|
2006-12-19 23:31:10 +01:00
|
|
|
}
|
2014-05-24 17:00:30 +02:00
|
|
|
if(len > 0 || write) {
|
2014-05-24 14:04:09 +02:00
|
|
|
stream->seekable = true;
|
2005-05-19 22:58:11 +02:00
|
|
|
stream->seek = seek;
|
|
|
|
}
|
stream: remove fd member
Stream implementations could set this to a unix file descriptor. The
generic stream code could use it as fallback for a few things. This
was confusing and insane. In most cases, the stream implementations
defined all callbacks, so setting the fd member didn't have any
advantages, other than avoiding defining a private struct to store it.
It appears that even if the stream implementation used close() on the
fd (or something equivalent), stream.c would close() it a second time
(and on windows, even would call closesocket()), which should be proof
for the insanity of this code.
For stream_file.c, additionally make sure we don't close stdin or
stdout if "-" is used as filename.
For stream_vcd.c, remove the control() code. This code most likely
didn't make the slightest sense, because it used a different type
for stream->priv. It also leaked memory. Maybe it worked, but it's
incorrect and insignificant anyway, so kill it. This code was added
with commit 9521c19 (svn commit 31019).
Untested for all protocols other than stream_file.c.
2013-07-12 22:07:07 +02:00
|
|
|
priv->fd = fd;
|
2005-05-19 22:58:11 +02:00
|
|
|
stream->fill_buffer = fill_buffer;
|
|
|
|
stream->write_buffer = write_buffer;
|
|
|
|
stream->close = close_f;
|
2006-12-19 23:31:10 +01:00
|
|
|
stream->control = control;
|
2014-04-30 11:19:53 +02:00
|
|
|
stream->read_chunk = 128 * 1024;
|
2015-03-09 11:31:38 +01:00
|
|
|
stream->streaming = true;
|
2009-07-07 01:26:13 +02:00
|
|
|
|
2005-05-19 22:58:11 +02:00
|
|
|
return STREAM_OK;
|
|
|
|
}
|
|
|
|
|
2007-12-02 14:22:53 +01:00
|
|
|
const stream_info_t stream_info_smb = {
|
stream: fix url_options field, make protocols field not fixed length
The way the url_options field was handled was not entirely sane: it's
actually a flexible array member, so it points to garbage for streams
which do not initialize this member (it just points to the data right
after the struct, which is garbage in theory and practice). This was
not actually a problem, since the field is only used if priv_size is
set (due to how this stuff is used). But it doesn't allow setting
priv_size only, which might be useful in some cases.
Also, make the protocols array not a fixed size array. Most stream
implementations have only 1 protocol prefix, but stream_lavf.c has
over 10 (whitelists ffmpeg protocols). The high size of the fixed
size protocol array wastes space, and it is _still_ annoying to
add new prefixes to stream_lavf (have to bump the maximum length),
so make it arbitrary length.
The two changes (plus some more cosmetic changes) arte conflated into
one, because it was annoying going over all the stream implementations.
2013-08-25 22:49:27 +02:00
|
|
|
.name = "smb",
|
|
|
|
.open = open_f,
|
2014-06-10 23:56:05 +02:00
|
|
|
.protocols = (const char*const[]){"smb", NULL},
|
2014-05-24 14:06:13 +02:00
|
|
|
.can_write = true, //who's gonna do that?
|
2005-05-19 22:58:11 +02:00
|
|
|
};
|