| Commit message (Collapse) | Author | Age | Files | Lines |
... | |
|
|
|
|
|
|
|
|
|
|
|
|
| |
Fix for the following build warning:
Compiling torture/cmd_vfs.c
torture/cmd_vfs.c: In function `cmd_open':
torture/cmd_vfs.c:275: warning: unsigned int format, different type arg (arg 3)
torture/cmd_vfs.c: In function `cmd_mknod':
torture/cmd_vfs.c:992: warning: unsigned int format, different type arg (arg 3)
sccanf had mismatched types for mode_t between formating parameter and var args.
(cherry picked from commit d10c386472175ceb312b9bcca07822a6df66a266)
|
|
|
|
|
|
| |
reported by Regan Heath <Regan.Heath@BridgeHeadSoftware.com>.
Jeremy.
(cherry picked from commit 1b839eb9e4a6312e638d1856d1225b170525da7e)
|
|
|
|
|
| |
Karolin
(cherry picked from commit 7f60557c4ebc8de45b0c1bceda2be8e50d88e3ef)
|
|
|
|
|
|
|
| |
...to silence -Wmissing-prototypes
Signed-off-by: Jeff Layton <jlayton@redhat.com>
(cherry picked from commit b08f07f84e448e56116b84ba5fa59b211e584822)
|
|
|
|
|
|
|
|
| |
...to silence -Wmissing-prototypes and some uninit'ed variable
warnings. Thanks to GD for the extra-paranoid compiler flags.
Signed-off-by: Jeff Layton <jlayton@redhat.com>
(cherry picked from commit bc5274eb66ebe40aea3ab917a20f2f353172ca93)
|
|
|
|
|
| |
Jeremy.
(cherry picked from commit 46a5c08b101f1c218ecd6397614dde1d13a9077a)
|
|
|
|
|
|
|
|
|
| |
cifs.upcall links to libraries that live under /usr, so installing it
in /sbin doesn't seem appropriate. Move it to EPREFIX/sbin instead
(i.e. /usr/sbin).
Signed-off-by: Jeff Layton <jlayton@redhat.com>
(cherry picked from commit fe280993dea71b87b6042d6aded389b10bcd0b56)
|
|
|
|
|
|
|
|
| |
When building on linux, default to building cifs.upcall. Throw a
warning if ADS support is disabled or keyutils isn't installed.
Signed-off-by: Jeff Layton <jlayton@redhat.com>
(cherry picked from commit 7f1193d3c83b0c19f17c8f70542491222c9644da)
|
|
|
|
|
|
| |
Make this match the non-ACL case.
Jeremy.
(cherry picked from commit 1ca6239b9f67caafed50db5f284df00c5988ba03)
|
|
|
|
|
|
|
|
| |
<fumiyas@osstech.co.jp>.
Fix for smbclient and libsmbclient.
Jeremy.
(cherry picked from commit 71d00ef2888834ebed2a387a111a95bac1d227ad)
|
|
|
|
|
| |
Karolin
(cherry picked from commit af05317606f12f2c02b09bd1286cefd10bc37476)
|
|
|
|
|
|
| |
Make sure that usernames are parsed using the correct separator.
Otherwise group memeberships in winbind may be result broken.
(cherry picked from commit a2c313182135fc4f7596a595c5143b7bb71a0bdf)
|
|
|
|
|
| |
Karolin
(cherry picked from commit b17f9ecc8e8beb40f798dd47f3440811e8d07e81)
|
|
|
|
|
|
|
|
| |
libnss_winbindd.so -> libnss_winbindd.so.2
libnss_wins.so -> libnss_wins.so.2
Michael
(cherry picked from commit d63cd755220aba591709917c729e028a913bec5d)
|
|
|
|
|
|
|
|
|
|
|
| |
This is all that is still necessary in 3.2.3+.
(The eloquent workarounds for libsmbclient and libsmbsharemodes
are removed.)
In 3.3.0, with the separation of libdir and modulesdir, even this
step becomes unnecessary.
Michael
(cherry picked from commit fe8448fe8f7ee0d33631366503163d3b2ee3eded)
|
|
|
|
|
| |
Michael
(cherry picked from commit 08b43cbd04cf8894e91f1182b222f8dd1c90659d)
|
|
|
|
|
| |
Michael
(cherry picked from commit e97c52d38424c45b34e5d3b5dc2f4b2b3a1b9b31)
|
|
|
|
|
| |
Michael
(cherry picked from commit cf13475d4d5cfe968d694d49b8fd0f6020c5a9d8)
|
|
|
|
|
|
|
| |
using the parent security descriptor type and flags instead
of using the passed in SD.
Jeremy.
(cherry picked from commit c22bf57329f16a45eb0954b72f8083270f6535e7)
|
|
|
|
|
|
|
|
| |
with write time,
just return what the underlying filesystem says. Trying not to confuse UNIX apps any more than necessary.
Jeremy.
(cherry picked from commit 4e06c71a12654d78c9a94fb023e372920bf7618b)
|
|
|
|
|
| |
Jeremy.
(cherry picked from commit 738729cad0b88a2f453d61d38e1088003afd0a9e)
|
|
|
|
|
| |
Karolin
(cherry picked from commit df138f23b920757076917553fa4bbbe413918cf7)
|
|
|
|
|
|
| |
Michael
(cherry picked from commit cdc24fbb195b1a5460c05fcd20d7ba81ad69ef22)
(cherry picked from commit 5359d8ae840dba48bb6f2163085d22b80108db2c)
|
|
|
|
|
|
| |
Michael
(cherry picked from commit e8abbfabde3da0844ffb4e2507084c139a70d503)
(cherry picked from commit 998b699f27630d3ea6d781da4f09c1cfd3e24511)
|
|
|
|
|
|
| |
Michael
(cherry picked from commit 206985dfda5a9f62df975629046b00a88ec666f5)
(cherry picked from commit 80d5e3621cac803c007e38e437d07f7dab2379aa)
|
|
|
|
|
|
| |
Michael
(cherry picked from commit 041875c64daba3d185b1954eb0eb9a21b2f41ee1)
(cherry picked from commit 17351dc1ea2be1d2478d6ae00d63ec8967539ab0)
|
|
|
|
|
|
| |
Michael
(cherry picked from commit f23183bbec55faf2d6496e04e73f8dd415a08d1c)
(cherry picked from commit 84810cd8a66503acb447e7c3bd439b76c735366b)
|
|
|
|
|
|
| |
Michael
(cherry picked from commit 4420cf6199e3c718a3dea84fe814d6ad6e83c2d8)
(cherry picked from commit fdaef16604064cbd0be75838f9d6359a3d7a8e1b)
|
|
|
|
|
|
| |
Michael
(cherry picked from commit c015e8e0cf4131f21305451943df13b81f51ea6a)
(cherry picked from commit e243a6a724fc820fa01aa3e16f18212ed6729415)
|
|
|
|
|
| |
Karolin
(cherry picked from commit eec57823cd6503339f8a54fed7dce0d4d41ab9a5)
|
|
|
|
|
|
| |
Michael
(cherry picked from commit 3eaa33e9df6d58ef93f13a840b38a063649fffbc)
(cherry picked from commit 165691927cdaaafc057de667294dff7a7bc8a991)
|
|
|
|
|
| |
Karolin
(cherry picked from commit 903868a474d4875807a131dffe74b5090c0dbcea)
|
|
|
|
|
|
|
| |
When alignment was in place, we pretended to send more data/params according to
the param_offset/param_length and data_offset/data_length parameters than would
actually fit into the SMB according to the NBSS length field.
(cherry picked from commit 2ae870aead5e0ea7e7f9f6f9730f989ae34755b9)
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
- only the first non truncating write causes
the write time update with 2 seconds delay.
It's not enough to check for an existing update event
as it will be NULL after the event was triggered.
- SMBwrite truncates always update the write time
unless the sticky write time is set.
- SMBwrite truncates don't trigger a write time update on close.
metze
(cherry picked from commit 142a9703ae19a467a23ee72429f899dae156df64)
|
|
|
|
|
| |
(cherry picked from commit dbe7a61be2beac50d1665e38ac374cefbbabec00)
(cherry picked from commit c2faa48abce1d656527b89f601e084e3ba70e36d)
|
|
|
|
|
| |
Jeremy.
(cherry picked from commit b2fcb8b6b17302e5ec29914f4e3dde853ffe5283)
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Ok, here's the fix for the write times breakage
with the new tests in S4 smbtorture.
The key is keeping in the share mode struct
the "old_file_time" as the real write time,
set by all the write and allocation calls,
and the "changed_write_time" as the "sticky"
write time - set by the SET_FILE_TIME calls.
We can set them independently (although I
kept the optimization of not setting the
"old_file_time" is a "changed_write_time"
was already set, as we'll never see it.
This allows us to update the write time
immediately on the SMBwrite truncate case,
SET_END_OF_FILE and SET_ALLOCATION_SIZE calls,
whilst still have the 2 second delay on the
"normal" SMBwrite, SMBwriteX calls.
I think in a subsequent patch I'd like to
change the name of these from "old_file_time"
to "write_time" and "changed_write_time" to
"sticky_write_time" to make this clearer.
I think I also fixed a bug in Metze's original
code in that once a write timestamp had been
set from a "normal" SMBwriteX call the fsp->update_write_time_triggered
variable was set and then never reset - thus
meaning the write timestamp would never get
updated again on subsequent SMBwriteX's.
The new code checks the update_write_time_event
event instead, and doesn't update is there's
an event already scheduled.
Metze especially, please check this over for
your understanding.
Jeremy.
(cherry picked from commit f2fb6321b6666a30ca7fa11bc8d395f1a1865bb2)
|
|
|
|
|
| |
Karolin
(cherry picked from commit 9082c77af4fb9fda6bb0a85810e454302130a71f)
|
|
|
|
|
| |
Jeremy.
(cherry picked from commit d7eab4b20af47401d281dd672e012d4eb96e5f4a)
|
|
|
|
|
|
|
|
| |
request.extra_data is not freed if there is no extra_data in response or
when there is some error happens in processing. This patch will free the
buffer right after processing a request before sending back a response.
(cherry picked from commit be6f12273f171a3eb1967d2299064e57d737f6a4)
(cherry picked from commit 72865f5e4ff30861d58b928baaf7be3373301f37)
|
|
|
|
|
|
|
|
|
| |
This is a step in fixing bug 5707.
Thanks to Igor Galić <i.galic@brainsware.org> for reporting!
Volker
(cherry picked from commit 1558a5c1977b1f87600ec487238fa8db009f41fd)
|
|
|
|
|
| |
Michael
(cherry picked from commit cc54b4d74171d27e7a0b09aff0376804ac7ab69b)
|
|
|
|
|
|
|
|
| |
When MS introduces a new PAC type, we should just ignore it, not
generate a parse error. New PAC info structures are supposed to be
backwards compatible with old ones
(cherry picked from commit 2971b926c835412b02c93ad1e30f1471bc0a3612)
(cherry picked from commit 843e9ebbf63f84270f8638a8e79538523b2148a8)
|
|
|
|
|
|
|
| |
(f321240fa91fa19c1131f119c42f64897d220682)
Michael
(cherry picked from commit cd3f4ee593e606e48cd104df222f8bda8e370a58)
|
|
|
|
|
| |
(cherry picked from commit 5ccdc58ce91ee40ca7171dd040191291aeb7fe02)
(cherry picked from commit 1361caecb355047001f8a351ec2e6f10d7f0e741)
|
|
|
|
|
| |
(cherry picked from commit 794e48b809036871287df8416a2c669b7e26f216)
(cherry picked from commit 3ce3f7f58402b98ce386bab1c40988e5ccd40d15)
|
|
|
|
|
|
| |
Michael
(cherry picked from commit 0d9f3dfc4c139938ee57b6cf60c29cf4ce404be7)
(cherry picked from commit 2381ec3b3f6a4798c15f4d3f3aee8caea8f48941)
|
|
|
|
| |
(cherry picked from commit 2d84b9a1024f68657f75aa7e0c4091b8c7afd194)
|
|
|
|
| |
(cherry picked from commit 59415cb8b3ce7981dbf576086e13675f343581a4)
|
|
|
|
| |
(cherry picked from commit 2a085d5343ab954e1bd60c11033506dc7c9040e3)
|