to send the signal
> even for mismatched uids, again look at it code.
Exactly because of that - p_cansignal behaves in it's own way, which
doesn't match the indended/documented kill(2) behavior. You're right
in a sence that plain uid check is not sufficient though
urned if any process could be
signaled.
IMO there should be an additional check in this condition:
if (p->p_pid <= 1 || p->p_flag & P_SYSTEM ||
p == td->td_proc || p->p_state == PRS_NEW) {
continue;
}
E.g. something like
* Dmitry Marakasov (amd...@amdmi3.ru) wrote:
> I'm helping to investigate some userspace issue [1], where kill(-1, SIGKILL)
> fails with EPERM. I've managed to isolate this case in a small program:
>
>
> ```
> #include
> #include
> #include
> #include
> #incl
to what manpage says, I see no way
for it to return EPERM: sys_kill() should fall through to the switch, call
killpg1() with all=1 and killpg1() if(all) branch may only set `ret` to
either 0 or ESRCH. Am I missing something, or is there a problem somewhere?
[1] https://github.com/NixOS/nix/issues/325
compatible).
If there's interest in this, I can refresh the patch and submit it.
--
Dmitry Marakasov . 55B5 0596 FF1E 8D84 5F56 9510 D35A 80DD F9D2 F77D
amd...@amdmi3.ru ..: jabber: amd...@jabber.ruhttp://www.amdmi3.ru
___
freebsd-stable
* Kostik Belousov (kostik...@gmail.com) wrote:
I've tried the second patch, it works fine. It would be very nice to see
it in 8.1, thanks.
--
Dmitry Marakasov . 55B5 0596 FF1E 8D84 5F56 9510 D35A 80DD F9D2 F77D
amd...@amdmi3.ru ..: jabber: amd...@jabber.ruhttp://www.amdmi3.ru
to be enough for anybody.
Another good thing would be to make it configurable at boot-time
or even better in runtime.
--
Dmitry Marakasov . 55B5 0596 FF1E 8D84 5F56 9510 D35A 80DD F9D2 F77D
amd...@amdmi3.ru ..: jabber: amd...@jabber.ruhttp://www.amdmi3.ru
time with a message
server is alive again). Also I've seen another strange thing - not
only the mount dies but the network is flooded with NFS traffic.
Last time I've seen it quite a while ago, so I don't remember the
circumstances and direction of the traffic.
--
Dmitry Marakasov . 55B5 0596
corruption if they rely on
locking.
I know - I have no processes that use locks on that filesystems.
Also there's only a single client.
--
Dmitry Marakasov . 55B5 0596 FF1E 8D84 5F56 9510 D35A 80DD F9D2 F77D
amd...@amdmi3.ru ..: jabber: amd...@jabber.ruhttp://www.amdmi3.ru
failed which
leads to file corruption.
Personally I definitely prefer the first.
Yeah, but I have mostly desktop-(NAS w/torrents) setup so I prefer
the second.
--
Dmitry Marakasov . 55B5 0596 FF1E 8D84 5F56 9510 D35A 80DD F9D2 F77D
amd...@amdmi3.ru ..: jabber: amd...@jabber.ruhttp
.
Any ideas?
PS. Diffs of corrupted blocks in a text format are here:
http://people.freebsd.org/~amdmi3/diff.1.txt
http://people.freebsd.org/~amdmi3/diff.2.txt
http://people.freebsd.org/~amdmi3/diff.3.txt
--
Dmitry Marakasov . 55B5 0596 FF1E 8D84 5F56 9510 D35A 80DD F9D2 F77D
amd...@amdmi3
* Daichi GOTO ([EMAIL PROTECTED]) wrote:
It is my pleasure and honor to announce the commitment of
latest unionfs improvements for 8-current, RELENG_7 and
RELENG_6. Now you can get more stable operation using
unionfs on latest 8/7/6.
This latest improvements give finstall and FreeSBIE works
* Dmitry Marakasov ([EMAIL PROTECTED]) wrote:
Well, I've temporary solved a problem. I've downgraded to 6.1, but then
I discovered that nvidia 9631 gives artifacts on 6.1 as well. So I've
also downgraded driver to 8776 and voila - now everything works (so I
was mistaken - I've used 8776, not 9631
* Dmitry Marakasov ([EMAIL PROTECTED]) wrote:
Update: after some research I've determined natre of this color
distortion. It seems like card interpretes each RGB8 value (24 bits, 8
for each color component) as RBG4 (12 bits, 4 bits for each component,
red-blue-green order).
Thus, color which
(GForce4 440 go). X log says to use the old 96xx version of
the driver.
I've used portdowngrade for that purpose. My GF3 is not supported
by 97xx as well.
--
Best regards,
Dmitry Marakasov mailto:[EMAIL PROTECTED]
___
freebsd-stable
Depth 24
Modes 1280x1024_135 1280x1024_108 1024x768 800x600
640x480 640x400
EndSubSection
EndSection
--
Best regards,
Dmitry Marakasov mailto:[EMAIL PROTECTED]
___
freebsd-stable@freebsd.org
16 matches
Mail list logo
