[PATCH] Fix bug #10430

[Mikhail Skorzhinskiy]

I've already tried to solve this bug[1] and submitted one patch[2]. Back
then, I've done nothing to ensure it will compile under master and have
not checked is it working or not. It was working in my environment and
was enough for me.

Now I've finally have moved to samba 4.5.1. Basic tests says that WORM
functionality works: writing from different initiator types are failing
under WORM protection.

Attached patch is made from current master (and it's compiling). So,
should I test it under current master? Or test that I've made under
4.5.1 is enough?

I'm also slightly confused, is there are anybody using this WORM
functionality (except me)? I would say bug is kind of blocking.

So, if somebody leave me comments about my little work, it would be
great.

o Links

  [1] https://bugzilla.samba.org/show_bug.cgi?id=10430
  [2] https://lists.samba.org/archive/samba-technical/2014-October/102944.html

--
Skorzhinskiy Mikhail
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 0001-modules-worm-wraped-more-system-calls-added-read_onl.patch
Type: text/x-diff
Size: 10927 bytes
Desc: not available
URL: <http://lists.samba.org/pipermail/samba-technical/attachments/20170116/49b35250/0001-modules-worm-wraped-more-system-calls-added-read_onl.diff>